SOAPUI TestRunner test case count and runner (teardown) test case count mismatch
Hi, Structure and flow of Project TestSuite Test Case 1 Test Step (REST request) Test Case 2 Test Step (REST Request) Test Step (Groovy script) (this script will call and execute Test Case 3 based on condition, test case 3 will be disabled state, if condition pass it will enable test case and execute and again it will be disabled Test Case 3 Test Step (REST Request) Problem Statement : If we execute above TestSuite via 'SOAPUI-TestRunner', number of test case executed count is correct, in our sample case : Total Test case count : 4 (which is correct, since test case 3 got executed twice via groovy script (Test Case 1 + Test case 2 + Test case 3 + Test Case 3), but if we try to get total Test case executed count from teardown its showing as 'Test case count : 2 Teardown script not considering test cases which got executed via groovy script Attached snapshots for reference Any help or support would be great, thanks
ReExecution Status is not getting Updated from test suite teardown
Hi Team, Greetings!! I am running a test suite andin the tear down script am re-executing the failure test cases. The issue is ,I am able to re-execute the failed test cases but the status of the test case are not getting updated even though testcase got passed on Re-Execution. Please help me out in this how to update status of the failure testcase Thank You!!
Setup and Tear down, as well as Try Catch questions.
Hello, I am fairly new to TestComplete, so please bear with me. I am using TestComplete to test a windows application. I am more used to the NUnit side of things. In NUnit, you can have setup and teardown functions that will run before any test as well as after any test, even if there is an failure in that test. Does TestComplete have this kind of functionality? If it does not, is there any easy work around to always be in a consistent state for each test? Also, I am trying a try catch block using JavaScript in TestComplete. Basically to try to close my app, and if it cannot, catch by writing to the log. My problem is, if inside the try look, there is an error, the test just stops. So, I am unsure why it just doesnt kick to the catch, and move on like nothing is wrong. Is this expected, and if so, what is the point of try catches in TestComplete. Thanks for all of your time.