Creating Test Scenarios
You can create Test Scenarios in Worksoft SaaS by assembling the Test Scripts.
Here is the step-by-step process to create test scenarios by assembling the Test Scripts you created and uploaded into the Test Script Library in Worksoft SaaS.
Click on the "Create" button on the top right-hand side when you are on the 'Test Scenarios' module to initiate this process.
1. Assemble the Scripts from your Script Library
Note that the Scenarios are set to status Work in Progress (WIP) by default. It will stay in this status until you 'Activate' the Scenario (which you can and should do once you finish all the steps and have successfully 'validated' (certified) the Scenario). More on this later.
You can optionally assign 'Labels' to the Scenario you are creating. Please refer to the article on Managing Labels on how to create and assign Labels to any automation asset within Worksoft SaaS. This is a very powerful feature that will help you find and maintain your automation assets easily and efficiently. We recommend you to use it as much as you can.
Now you are ready to start your "Assembly" of your Test Scripts for the Scenario.
This is a very easy process if you know what Test Scripts you want to assemble into a Scenario.
Finding the Scripts you want to add to your Assembly by using Filters and/or Search:
You can search for the Scripts that you want to include from your Script Library or use the vertical scroll bar on the right and scroll up or down to find the Script(s) you are interested in assembling into the Scenario. Or you can "filter" the Scripts in your Library to look at only Scripts that are for a specific Product and/or attached to specific Label(s). Filtering will help you look for the Script from a smaller subset of Scripts from your Library.
You can optionally assign 'Labels' to the Scenario you are creating. Please refer to the article on Managing Labels on how to create and assign Labels to any automation asset within Worksoft SaaS. This is a very powerful feature that will help you find and maintain your automation assets easily and efficiently. We recommend you to use it as much as you can.
Now you are ready to start your "Assembly" of your Test Scripts for the Scenario.
This is a very easy process if you know what Test Scripts you want to assemble into a Scenario.
Finding the Scripts you want to add to your Assembly by using Filters and/or Search:
You can search for the Scripts that you want to include from your Script Library or use the vertical scroll bar on the right and scroll up or down to find the Script(s) you are interested in assembling into the Scenario. Or you can "filter" the Scripts in your Library to look at only Scripts that are for a specific Product and/or attached to specific Label(s). Filtering will help you look for the Script from a smaller subset of Scripts from your Library.
Picking (Selecting) the Scripts into your Assembly:
Once you find a Script that you want to assemble into the Scenario, you should click on one of the 2 icons under the column caption 'Pick'.
- The icon with just the + sign indicates that the Test Script is not 'parameterized'
- The other icon indicates that the Test Script is 'parameterized' (ready to be included as part of a 'Data-driven' execution).
You have the option to include the parameterized version of the Script into the Library or the non-parameterized version.
Please refer to the topic of 'Data-Driven Testing w/ Worksoft SaaS' to learn more about parameterization. (To let a Test Script be used a part of a 'Data-Driven' execution, you have to 'parameterize' the Test Script (wherein you map the instructions within your Script to 'Attributes' of a Data Definition).
A Test Script that is 'parameterized' always has a 'non-parameterized' equivalent. This is because every Script that is created using QaSCRIBE or uploaded into Worksoft SaaS has embedded in it, for lack of better words, hard-coded data (input or expected output). We call Scripts with 'hardcoded' data 'non-parameterized' Test Scripts. )
Scripts that you 'pick' get moved to the 'Selected Scripts' grid at the bottom automatically.
Continue to add other Scripts that you need in your Library.
Can I pick the same Script multiple times into your Assembly?
Yes, you very well can.
If your assembly requires the same script to be embedded multiple times, you can add the same Script multiple times into your assembly by clicking on the 'Pick' icon multiple times. The Count column in the Script Library Grid on the top shows the number of times a Script is included in the Scenario.
Removing Script(s) from your Assembly:
If you need to remove any Scripts from your Library because you accidentally picked the wrong Script, just click on the 'red' minus icon under the 'Actions' column for the Script (row) that you want to remove from the assembly.
Re-arranging Scripts within your Selected Scripts (Assembly):
Don't worry about finding and picking your Scripts in the exact order you want them in the 'Assembly'. Once you have all the Scripts you need in your assembly show up in the 'Selected Scripts' grid, you can just drag-and-drop the scripts into the right sequence. Easy isn't it?
In the screenshot below for illustration purposes of this re-arranging feature, 5 Scripts are shown in the Assembly.
When 'picking' the user has picked the Scripts in some random order.
But, wait you accidentally picked the 'WIP' versions for the last 2 Scripts in your Library. To correct this you may be thinking that you need to 'remove' those Scripts from your Assembly and find & 'pick' the 'Active' versions, and then rearrange the Scripts in the right order. You are right. You could do that but in Worksoft SaaS, you don't have to do that. There is an easier way.
Replacing 'WIP' version of your Scripts w/ 'Active' versions ... one-click-away:
Just click on the green 'replace' icon right next to the WIP (or 'Active') status and that replaces your 'WIP' version with your 'Active' version (or vice versa). It's that easy.
Replacing 'Parameterized' Scripts w/ 'Non-Parameterized' .... again, just-one-click-away:
If you accidentally picked the 'non-parameterized' Script when you in fact needed to pick the 'parameterized' you could remove the Script from your Assembly, go into the 'Test Script Library' grid above, find and pick the 'parameterized' copy of the same Script into your Assembly, and then adjust the sequence of your Scripts in your Assembly.
But instead, you could just click on the green 'replace' icon immediately to the right of the Test Script name that replaces your 'non-parameterized' copy with your 'parameterized' copy (or vice versa). It's that easy.
Data-Driven Test - Implicit and Explicit Data Loops:
If you picked one or more 'parameterized' scripts into you Assembly, your intention very well is to make your Scenario to execute in a 'Data-Driven' mode (where your test inputs and/or expected test outputs are read from 'Data File(s)' that you uploaded into Worksoft SaaS).
Worksoft SaaS supports both Implicit(ly identified Data Loops) and Explicit(ly user created Data Loops). To define the Data Loops, you simply toggle the 'View' in the 'Selected Scripts' grid [aka your Assembly] from 'Assembly' view to the 'Data Loops' view. This gives you the tools under the 'Action(s)' column (first column) to add/edit/remove your Data Loops.
Please refer to the topic of 'Data-Driven Testing w/ Worksoft SaaS' to learn more Implicit and Explicit Data Loops and Data-Driven testing in Worksoft SaaS.
Done with your Assembly? How do you proceed to next step?
Once you are done assembling your Scenario, you can click on one of the 'Save' buttons.
Why are there so many buttons? Just simply, Worksoft SaaS gives you choices so that you pick the right option that suits your current need in the context of this Scenario you have just assembled.
You can Save with a particular status (WIP or Active) and just 'exit' or proceed to 'Validate' your Scenario. In Worksoft SaaS, 'Validation' means 'certifying' that the web (or mobile) application works well for your Test Scenario in one or more the Environments where the application is deployed/accessible from, and running tests from one or more browsers, operating systems, and desktops/devices.
If you Save & Exit, you can come back later and continue with the next steps that are left for you to complete the creation and certification of your Scenario.
If you don't want to Exit, you can proceed to continue by choosing 'Save as WIP & Validate' or 'Save as Active & Validate' buttons.
2. Bind Data to your Assembly
This is the 2nd tab in your 4-step workflow for creating a Scenario.
If there are no 'bindings' needed for your Scenario, Worksoft SaaS will skip this tab (step) for you and directly take you to the next tab 'Specify Testing Context(s)'.
Please refer to the article on 'Binding Data' to your Scenario or Run Definition for learning how to bind 'Data Files' for Data-Driven testing or binding Files that allows you to dynamically let Worksoft SaaS feed files (of type images, PDF, videos, audio files, etc) into your tests as browser upload from within your test scripts.
For now, we will proceed to specify Testing Contexts.
3. Specifying Testing Context(s) for your Scenario
'Testing Context' in Worksoft SaaS is a specific combination of:
- One of the environments where your web/mobile application is deployed at or accessible from
- The platform or device on using which you want to run the test. This will include cloud platform you want to use to run your test, the browser/version, operating system/version, device/version, screen orientation [landscape|portrait], screen resolution, etc
- The level of visual and/or textual logs (screenshots, videos, Selenium/WebDriver/Appium/Selendroid logs, cloud platform logs, etc) you want Worksoft SaaS to generate when the test runs
- Optionally, specific advanced settings you want Worksoft SaaS to use like Geo-Coordinates, Language, Timezone, etc to simulate users coming from specific locations in the world or users using specific language in their browsers or users being in a specific timezone
- You can create as many Testing Contexts as you need to fully certify your application for the Test Scenario that you just created.
Click here to know about Project Level Groups of Testing Platform.
The screenshot below illustrates numerous Testing Contexts created.
Each column in this screen shows the configuration of each parameter that is configured as the context of your Test Run. To view the specification, mouseover on the icon.
Please refer to the articles "Testing Contexts - Basic" and "Testing Contexts - Advanced Options" for details on the various options available when creating/editing Testing Contexts.
4. Execute (Validate) the Scenario
Once you create one or more Testing Contexts for the Scenario, you are ready to execute the Scenario for all or subset of the Testing Context(s). We call this 'validation' (aka 'Certification') of the Scenario.