Usually, the test automation is meant to run autonomously, without the need of user intervention. However, there may be causes (usually, during debugging), when we need to pause the test and manually set/check something. The most common way is doing it via breakpoints. However this is often not the fastest/best way how to pause the test! Setting breakpoint means that one needs to go to the code. And if the paused step is located in reusable recording/code module, the test may pause at places you are not interested in. I just experienced this with test I'm currently working on. The solution I came with is using simple custom dialog, which is shown during the test and which contains certain value I need to copy from actual step.
What I did was creating a new code module, which I called PAUSE_EXECUTION. I'm placing it wherever I need to pause the test.
Feel free to modify the module according your needs (add more labels/inputs, etc...).
Best practices, code snippets for common functionality, examples, and guidelines.
2 posts • Page 1 of 1
You do not have the required permissions to view the files attached to this post.
That would be a nice candidate for https://github.com/ranorex/Packages/tre ... ionHelpers ...