Forum Discussion
Pragmatics__Inc
13 years agoOccasional Contributor
The best way to recreate this problem is to drag and drop a new test case within a test suite. Note, that I've seen this happen eventually throughout the course of working with 4.5, but this is the quickest way to create the issue.
Steps:
1. Open a test suite with existing wsdl test steps.
2. Create a new wsdl test step.
3. Drag the new test step before some other test step in the test suite.
Expected Result: The test step is moved and the user can open it and look at the test steps, or look at any other test step in the tree.
Actual Result: The test step is moved. Opening it to the test steps won't respond. Attempting to open other test cases in the tree to show the list of test steps will fail. Eventually, all of SoapUI 4.5 will no longer refresh and appears unresponsive. SoapUI must be closed.
Steps:
1. Open a test suite with existing wsdl test steps.
2. Create a new wsdl test step.
3. Drag the new test step before some other test step in the test suite.
Expected Result: The test step is moved and the user can open it and look at the test steps, or look at any other test step in the tree.
Actual Result: The test step is moved. Opening it to the test steps won't respond. Attempting to open other test cases in the tree to show the list of test steps will fail. Eventually, all of SoapUI 4.5 will no longer refresh and appears unresponsive. SoapUI must be closed.