Activating a Test Script in 'WIP' status
Quick Links:
- Steps to activating a test script
- What if one of you peers locks a test script before you clicked on 'activate' the same script
- Impacts on 'Dependent Entities' when you attempt to 'activate' a test script
Steps to activating a test script:
When you are in the 'edit' mode or a 'view' mode of a WIP version of a test script, to 'activate' it, click on the 'Activate' button on the top right hand side of the screen.
Please remember that you will not be able to make any changes to the 'Active' version of a test script. If you attempt to 'edit' an active script, Worksoft SaaS will create a copy of your 'active' version in 'WIP' status. You can then make the changes you want to make to the 'WIP' version.
It is possible that by the time you decide to activate a currently 'WIP' script and click on the 'Activate' button, someone else on your team enters the same script in the edit mode, and locks that script from edit by others. In this case, if you attempt to 'activate' it, you will see an alert that someone else locked it. You will not be allowed to 'activate' the script until your peer has removed the lock on it.
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. Then once you are done with your changes, while the lock exists on the script, click on 'Activate' button.
Impacts on 'Dependent Entities' when you attempt to 'activate' a test script:
Impacts on 'Dependent Entities' when you attempt to 'activate' a test script:
When you are in the 'edit' mode or the 'view' mode of a WIP version of a test script and attempt to 'activate' the script, by clicking on the 'Activate' button, if there are any dependent entities that will get impacted.
If there are any other automation entities (test scenarios, run definitions, data definitions, data files, etc.,) that will get impacted as a result of the automation, Worksoft SaaS will present to you a screen that lists the impacted entities and suggests various options for decisions you could take to resolve the impacts or dependencies.
Once you specify your preferences for actions on that screen and click 'Continue' the 'Activation' process will complete. Please note that depending on the number of impacted entities, the activation process may take several seconds to minutes.
You will be able to see an audit trail of all impacted objects if you access the 'Activity History' screen.