Active TestSuites and Projects keep running after closing
When you have a TestSuite with several response TestCases, and you run the whole suite, if you click the TestSuite's close button, then all of it's cases keep running in the background.
Likewise, if you run an entire Project, and then close it before it's finished, all of its suites and cases will continue running in the background.
Reopening the suite or project does not re-establish a connection to the closed instance, so you can't use soapUI's UI to make the TestSuite or Project stop once it's in this state.
This is a long-standing issue that affects all versions of soapUI and Ready! API.
Steps to Reproduce (steps are similar for Projects):
1. Create a TestSuite with at least 2 or 3 Cases with Soap Response test steps.
2. Double-Click the TestSuite
3. Click Run, to run all cases
4. Click the TestSuite's X button to close it
5. Run some requests, that point to your listeners from this suite
Expected Result:
At step 4: soapUI should display a dialog, asking if you want to leave the test suite running, stop it, or cancel (similar to the dialog that displays when you try to close a running TestCase)
a. If you choose to close and leave the suite/project running, then the next time you re-open the suite/project, soapUI should re-connect to the running instance, so that you can regain control of it.
Actual Result:
At step 4, the Suite closes without any prompt
At step 5, your requests will receive responses from the invisibly running listener test cases.
Work Around:
Either close and reopen soapUI, or exhaust all of the response cases by pushing enough requests to trigger them.
I've seen this behavior cause people issues on many occasions, because they'd closed a running test suite earlier and were trying to run different tests, but the invisibly running suite kept interfering.
Likewise, if you run an entire Project, and then close it before it's finished, all of its suites and cases will continue running in the background.
Reopening the suite or project does not re-establish a connection to the closed instance, so you can't use soapUI's UI to make the TestSuite or Project stop once it's in this state.
This is a long-standing issue that affects all versions of soapUI and Ready! API.
Steps to Reproduce (steps are similar for Projects):
1. Create a TestSuite with at least 2 or 3 Cases with Soap Response test steps.
2. Double-Click the TestSuite
3. Click Run, to run all cases
4. Click the TestSuite's X button to close it
5. Run some requests, that point to your listeners from this suite
Expected Result:
At step 4: soapUI should display a dialog, asking if you want to leave the test suite running, stop it, or cancel (similar to the dialog that displays when you try to close a running TestCase)
a. If you choose to close and leave the suite/project running, then the next time you re-open the suite/project, soapUI should re-connect to the running instance, so that you can regain control of it.
Actual Result:
At step 4, the Suite closes without any prompt
At step 5, your requests will receive responses from the invisibly running listener test cases.
Work Around:
Either close and reopen soapUI, or exhaust all of the response cases by pushing enough requests to trigger them.
I've seen this behavior cause people issues on many occasions, because they'd closed a running test suite earlier and were trying to run different tests, but the invisibly running suite kept interfering.