Lesson 3 Topic 3 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 3 :: Topic 3
1. Scenarios
To combine multiple Test Scripts and execute them at a time, we use a feature called 'Scenario'. 'Scenario' is Level 2 in this case.
A Scenario is typically used to represent a Business Use Case/Scenario that can be independently tested or combined with other Scenarios.
A Scenario is typically used to represent a Business Use Case/Scenario that can be independently tested or combined with other Scenarios.
2. Predecessor/Successor Scenarios
We can also use a Scenario to separate the core actions from the Prerequisite/Subsequent actions.
For Example: While testing an eCommerce site, our core action is to check if the product selected is added to the cart correctly. For this, we may need to log in as a user (every time) which is a pre-requisite action and log out (every time) which is a subsequent action.
In most cases, such actions may also be required to be reused in combination with other core actions.
In Worksoft SaaS, you can create Scenarios and use them as Predecessor Scenarios and/or Successor Scenarios by combining with the core Scenario. All Scenario types are created alike, however, the way a Scenario is linked determines if it is being used as Predecessor or Core or Successor Scenario. In this way, Scenarios can easily be reused based on your needs.
In Worksoft SaaS, you can create Scenarios and use them as Predecessor Scenarios and/or Successor Scenarios by combining with the core Scenario. All Scenario types are created alike, however, the way a Scenario is linked determines if it is being used as Predecessor or Core or Successor Scenario. In this way, Scenarios can easily be reused based on your needs.
3. Entity Versions
Automation entities like Test Scripts and Scenarios can have up to 3 versions.
In Worksoft SaaS, we save our entities in the WIP (Work in Progress) version until we certify the automation because a WIP version allows you to make changes.
Once the Certification process is complete, they can be saved in the 'Active' version which protects the entity from making any further changes and hence can be used to execute tests, then the WIP version acts as a Copy.
If the entities are not in use, we can also inactivate them (Inactive)