So I have a custom behavior called "Test", and it's set to ⌘-shift-pgdn. It's supposed to just play the Submarine sound. But when I hit that shortcut, it just plays the usual error sound.
This is a test case for trying to get the Unlock behavior to run a Perforce script to unlock files.
Related
In UFT 14.50 (but I don't think this is version-specific), I face the following problem:
For action-based GUI tests, I can configure for each test using File/Settings/Run what should happen in case of error:
For BPT GUI-based components, I cannot; there is no "Run" section:
Also in the application area for the component, which would be the second place where it would make sense to put this setting, there is no such setting.
I do understand that I can set this setting programmatically using <App>.<TestOrComponent>.Settings.Run.OnError.
I also understand that one can configure this setting in the execution setting for each component call in a BPT test flow script, or BPT test script, but what about interactive component execution for debugging reasons -- I have to change this setting in every component programmatically during runtime if I want to define/change this setting when doing debug runs in the UFT IDE, is this correct?
Bonus question: What is the rationale to hide this setting for a given component?
It's a good question. It's one i had to think about as there are quite a few components involved.
You build your code for BPT application areas in UFT but the BPT test itself is designed to be managed and executed from ALM. Around version 11 or 12 HP (the vendor at the time) updated the remote agent to have "debug mode" (the top option in these settings):
If you've not seen this you window, you get it from right clicking on the remote agent on your system tray:
(you can also set it by updating the mic.ini file - shout if you need more info on this)
I've not used BPT for about a decade, but that option in the remote agent I am very aware of. POTENTIALLY The run option you're after doesn't exist because, for BPT and it's aLM dependency, it's now all controlled through that debug run setting.
With it CHECKED, when you run a test from ALM you get the popup on error
With it UNCHECKED, when you run a test from ALM, if it hits an issue the error popup is suppressed.
You don't need to set your options programatically.
Bonus points answer: Logically this makes sense as you're potentially kicking off an entire test set from ALM and if you had 1 bad object/line in the first test and it blocked an entire overnight run you'd be fairly angry. At least this way you have your local machine as a deubg run but all remote execution machines have it unchecked so they just keep going. It becomes a machine configuration and not a script configuration.
If this doesn't work as you expect there are other ways of using a common function library with environment variables to set all to debug or all to carry-on mode.
I'm making a BB10 app with a headless component that's normally supposed to run nonstop, except when a certain field in its QSettings changes (to save battery power).
I tried looking everywhere for the documentation. But I still can't find out how to make a headless app terminate itself.
You can get notified every time your settings file change using QFileSystemWatcher and calling bb::Application::instance()->quit() when a certain QSettings value changes. Here's an example from BlackBerry that uses QFileSystemWatcher in headless to get notification whenever the QSettings file changes.
I prefer using invocation or my own headless communication mechanism though, you can see an exemple of how I usually deals with terminating the headless app here.
I am running a launcher in publish instance,the launcher doesn't invoke the workflow when run mode is publish or publish and author but it works when I make run mode as author
Can someone help me with this behaviour of AEM?
Wrokflow launchers are tied to run-modes and you can change the behavior to run to either or both of them. The default dialog height is less hence it is not visible you need to scroll down.
Taken from the Adobe documentation:
When using one of the above run modes (author, publish, samplecontent, nosamplecontent), the value used at installation time defines the run mode for the entire lifetime of that installation.
For these run modes you cannot change them after installation.
You cannot use runmodes author AND publish at the same time (I wonder what AEM will do if you try to set both runmodes) and switching the runmode is also a bad idea.
See https://docs.adobe.com/docs/en/aem/6-0/deploy/configuring/configure-runmodes.html for details.
There must be something wrong with your instance. Any log messages?
I have some problems running FlexUnit tests in IntelliJ.
Every time I execute test, Internet Explorer (which is not even set as default browser) pops up and blocks unit test, i.e. blocks it as add so I must allow access through that dumb top bar and then another confirmation and then finally test runs. Is there any way to reconfigure it to another browser or to run it some other way so I just hit the Run button on Idea and I can see results right away?
Thank you for help
As you are using Windows have a look at the first comment by Alexander Doroshko in this bug report: http://youtrack.jetbrains.net/issue/IDEA-49795
Current behavior:
if 'Use system default browser' is selected at Settings | Web Browsers | Default Web Browser then swf/html is started in default OS application (either default browser of standalone Flash player)
if default browser is overridden in IDEA then it is always used both for swf/html.
It would be more convenient if standalone Flash player is used for swfs independently of this setting as soon as it is OS default program for sfws.
I recommend to configure the stand alone flashplayer executable for executing unit tests. As you can also see from the report this has been improved in IDEA 10.
I would like to know if it is possible to configure Dr. Watson to silently dump a crashing process without popping up any error dialog box?
We need this because I run a set of integration tests with some applications. We don't want the tests to be blocked by an error message box. We need a way to make Dr. Watson silent but still dump the image when the process crashes.
Best,
Dr.Watson itself is silent by default. anyway, if you want to control the way Dr.Watson works, enter "drwtsn32.exe" at a command prompt to display the configuration dialog for this software. also, to install Dr.Watson as the default debugger, use "drwtsn32.exe -i".
the settings for the default debugger is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug. the Auto value should be set to 1 for the system to automatically launch the default debugger. in your case, it is mandatory to set this value to 1.
once all the above things are setup, you can instruct Windows to stop displaying the "X has encountered a problem and needs to close" dialog. on Windows XP, this is controlled in the System Control Panel, on the Advanced tab, the Error reporting button on the bottom of the dialog allows to control how the system reacts when an error occurs. (on other versions of Windows, there should be something similar, search for "Error reporting" on Google)
with the debugger set to auto, Dr.Watson properly configured and error reporting disabled, the system should not show any dialog when a crash occurs.