Execution was stopping in Test Executer
When more than two Modules are kept for execution in Test Execute(version 11), execution gets stopped and the tool gets struck.
Forum Discussion
3 Replies
I'm not sure I understand the question. What modules are you executing and what code is in there? Are you getting any error messages? By tool getting stuck, do you mean you can't actually exit it (it's hung)?
Please give more detail so we can help you better.
Module here describes many number of tests(i.e., each test describes a transaction) regarding one menu in the application. While I keep more number of tests for execution at night then it was not completed and by the morning when I see the execution was hanged, it neither stopped nor continued..
Without more information about what code/test operations you're executing, etc., there's not a lot we can tell you. A "hung" test run probably means that you have put the test code into some sort of infinite loop.
Please provide examples of what you are executing.
