soapui setup script not executed when test case or test step run from java
Hi, When I try to run an individualtest case or a test step in a test suitefrom Java , The set up script for the test suite is not executed ! Any way to run this setup scrip explicitly ? or any other work around except having individual set upscripts for a test case ?
The new method added is not saved on test case on exit
Hi, I have a project for each functionality. For each project I have at least 3 endpoints (dev, test, uat) and different methods (for dev and test for valid or invalid requests). I've cloned the test suit for test to create the uat one and I've added the right method for that (first I've created it using the clone functionality, secondly I've created it from scratch). I saved the project, I saved all the projects and I exit. Next time login the method used by uat test cases is the same with one used on test which means the save wasn't taken in consideration. Any suggestion? It is quite urgent. Thank you!Ability to use tab to move within test steps
As a user, I need an easy and accessible way to navigate the screen while creating or editing a test case. Currently, you cannot use tab to move to the next text box when creating or updating a test case. It is also very difficult to click to the next test step without it creating a second step below the step you're working on.
Import new Test Steps section (Test Steps, Test Data, and Expected Results) to an existing Test Case
The user should be able to create an Import map and file to load new Test Steps (at least Test Steps, Test Data, and Excepted results) to a pre-existing Test Case in the Test Repository. Maybe by using the Test Case Id as a unique identifier for the Import processing.Ability to reference a test case within another test case
When creating and executing test cases, having the ability to reference a test case within another test case step/detail will save time, effort, and confusion for users. Being able to just reference an existing test case, instead of re-writing it, will increase efficiency as the user creating the test case and the user who are executing the test case (this allows users to either navigate to the reference test case to follow, or skip it because they already have that knowledge/know the steps.
