Saving a Test Script in 'WIP' status
Quick Links:
- Steps to saving a test script after you are done with the changes
- What if one of you peers locks a test script after you started editing it
- Validation/Error messages when you attempt to save a test script
Steps to saving a test script after you are done with the changes:
When you are in the 'edit' mode of a WIP version of a test script, to save the changes you have done to it, click on the 'Save' button on the top right hand side of the screen.
- Move the test script from one product to another product
- Assign a data definition to the test script so that you can parameterize the targets an/or values with the test instructions of that script
- Assign a data definition that is different from the one assigned previously
- Enter or change the description for the test script
- Lock it from edit by others
- Unlock a previous lock you set on it
- Added it to your 'Favorites'
- Removed it from your 'Favorites'
It is possible that if you start editing a test script that you did not lock from edit by others, someone else on your team enters the same script in the edit mode, and locks that script from edit by others. In this case, after you make some changes to that script, if you attempt to 'save' it, you will see an alert that someone else locked it. You will not be allowed to save the changes you have done.
Therefore, we strongly recommend that you lock a script from edit by others before you start making changes, especially if you know that in your project more than one team member owns the responsibility of creating and maintaining the test scripts.
Validation/Error messages when you attempt to save a test script:
Validation/Error messages when you attempt to save a test script:
When you are in the 'edit' mode of a WIP version of a test script and attempt to save the changes you have done to it, by clicking on the 'Save' button, if there are any validation rules that are violated by the changes you made to the script, you will see one or messages appear on the screen. You must resolve those items and reattempt the save.
Sometimes, the 'Save' button is disabled if Worksoft SaaS determines that there are certain types of errors in the changes you did. In such a case, the tooltip on the disabled 'Save' button usually provides as clue to you as to why you are not allowed to save the test script.
At a high level, the following types of violations will trigger the validation messages or disabling of the save button that prevents you from saving your changes:
- The command name in one or more of your test instructions is not supported in Worksoft SaaS
- No value was passed into the target field and/or value field when the command expects a value to be passed
- The looping constructs have no instructions within them
- The conditional constructs like if, else are not correctly built.
- There are no test instructions within your test script
- Someone else on your team locked the script from edit by others after you had entered into the edit mode of a particular script
- You used commands that are not supported for the product type of the product that a script belongs to. For example, if you use commands that are meant for testing native mobile app as part of a test script that is meant to test a web app.