I want to have standalone mode and flow mode in the same suite but it shows error such as "Ambiguity between: fixture dbfit.fixture.ExecuteProcedure AND executeProcedure()".
This is because standalone mode is getting executed and then flow mode.
When I changed the names so that flow mode is executed first and then stand alone mode, it starts working.
Can, anybody tell me how to close standalone mode so that flow mode can be started.
Related
I use newPage() in playwright, in order to have chrome cleaning the memory...
but when I launch the scrapper in headed mode, this newPage() (cf. playwright API) interrupts me each time when I am coding in vs code for example.
How to launch chrome, or set an option in playwright to avoid this behaviour ? I would like to use newPage() in headed mode without being disturbed in tasks workflows?
Tks,
While executing runAppInBackground() for Android application through Appium the app gets restarted but when executed the same manually couldn't be able to reproduce the same. I Would like to deep dive into implementation of a runAppInBackground() method to reproduce the same issue in a manual way.
You need to look behind the code of runAppInBackground
From java client side (your test code) perspective, it is a single call to Appium server:
POST "/session/:sessionId/appium/app/background"
If you continue looking into where its implemented on server side, you finish with appium-android-driver function.
In short what it does:
Get current activity and package
Press physical Home button
Wait for time you provided as argument (seconds)
Bring up back in focus based on different conditions; from the code you can understand what activity is being started
Basically its a sequence of adb shell commands, that you can run from terminal.
My guess is that step 4 you did manually may differ from what Appium is doing: different activities/arguments for activity been called
I'm using a windows 10 machine. I'm also running a docker container that is running a rails application. Whenever I make a change to any server side code (i.e controllers or models) I'm required to do a docker restart app.
However my friend is using the same container on his apple machine but when he makes changes to any server side code he does not have to restart his app.
Why is this?
Rails has a configuration option (config.cache_classes) that specifies whether or not your application code should be cached in memory between requests. Having this option set to true will require you to restart your app if you make changes; having it set to false reloads your code on every request, so you don't have to restart.
It is recommended to set this to false in the development environment only, because Rails works faster if it doesn't have to reload your code every time it starts processing a request. In production, you should leave it set to true.
I am using a BBB with the Debian distro. I access Cloud9 (192.168.7.2:3000) via Chrome on my Windows 7 machine. I am able to access existing demo js programs and have written a test program (myblink.js). The editor and overall system works fine.
But when I try to run the program, nothing happens for a few seconds, then eventually, it appears to stop on the first line (which becomes highlighted yellow). When this happens, the debugger panel pops out and the bottom window shows that the "debugger listening on port 15454" and I have the option to stop the program. At this point I can step through the program, well, at least to the point where there is some asynchronous events handling required.
However, if I run "node myblink.js" app from the bash tab in Cloud9 or from a shell (via putty) it works perfectly fine.
Do I have to set anything up to enable debugging? Or is it too much to expect from the debugger and a BBB system?
I am using webstorm. And I have setup a small sample app. Running the app displays the following in the output window
C:/dart-sdk/bin/dart.exe --ignore-unrecognized-flags C:/Users/testuser/WebstormProjects/TestDart/TestMe.dart
You are using Windows
Process finished with exit code 0
but when debugging it just sits there with the following output
C:/dart-sdk/bin/dart.exe --ignore-unrecognized-flags --debug:57939 C:/Users/testuser/WebstormProjects/TestDart/TestMe.dart
I have a breakpoint set in the main() funciton on this line, but it never hits it
stdout.write("You are using ");
I have no firewall and also I don't think i need dartium installed as this is just a standard console application that prints things out.
Anyone have any success?
thanks
Debugging Dart console application doesn't currently work:( Please watch WEB-9937 to be notified on any progress