In software testing life cycle, the tertiary stage is Test Design, inwards that tertiary stage of STCL Test Scenarios, Test cases as well as Test Design are created.
Many QA peoples oftentimes larn confused inwards betwixt Test Scenario as well as Test Cases as well as few of them fifty-fifty reckon both are same. The output from the Test Scenario is considered equally a input to assay cases. Few examples are given down. We volition verbalise over each term i past times one. Lets start alongside Test Scenarios.
Test Scenarios:
Test scenarios are too called assay status as well as it is real slow to notice out the assay scenarios nosotros merely take away to read requirements properly. For i assay Scenario at that spot tin last a multiples assay cases.
Scenarios tin last considered equally a broader indicate of thought as well as shorter indicate of thought also.
See the next examples
Example - 1 : login page
Requirements -
- Login page.
- Login page should direct hold shout back me button.
- Login page should direct hold forget password option.
- Login page should direct hold reset button.
These are the requirements for the Login modules.
Test Scenarios: (from Broader prospective)
- Evaluating the login page.
- Evaluation the shout back me button.
- Evaluation the shout back me button.
- Evaluation the shout back me button.
These are the assay scenarios for the login page. Scenarios may varies companionship to companionship about companionship facial expression for depth scenarios as well as about companionship reckon equally broader manner.
Example 2: Inquiry form
Requirements :
- Inquiry shape should direct hold Name, contact number, electronic mail id, as well as description field
- Inquiry shape should direct hold Update option.
- Delete functionality for Inquiry Deletion.
- Suppose these are the few requirements for the Inquiry form.
Test Scenarios :
If nosotros reckon scenarios equally broader prospective. Then scenarios equally shown follows.
- Evaluate Inquiry form.
- Evaluate Update functionality of the Inquiry form.
- Evaluate Delete functionality of the Inquiry form.
Some companies reckon scenarios equally follow also
- Evaluate the Name patch of Inquiry form.
- Evaluate the Contact pose out filed of Inquiry form.
- Evaluate the electronic mail Id patch of Inquiry form.
- Evaluate the Description patch of Inquiry form.
- Evaluate the Name patch piece editing the question form.
- Evaluate the Contact pose out patch piece editing the question form.
- Evaluate the electronic mail Id patch piece editing the question form.
- Evaluate the Description patch piece editing the question form.
- Evaluate the Delete functionality of Inquiry form.
These are ii ways nosotros tin notice the scenarios. Some companies prefer root way other prefers minute ways.
Lets run into how tin nosotros write the Test cases for Derived Test Scenarios.
Test Cases:
Test cases are similar a steps, how nosotros are going to assay each as well as every requirement, it is similar a performing pre-created steps as well as merely verify the output whether it matches alongside expected output or not.
Test cases has many things similar assay instance id, objective,pre-requisite, steps, assay data, expected output, actual output, status/result as well as remark, i time to a greater extent than these fields may vary companionship to company. Lets run into the important of each field.
Test instance ID: it is unique id for each assay case.
Objective: it is the objective of test. For illustration : banking firm check the login functionality for valid credentials.
Pre-requisite: it is the pre-conditions which is take away or mandatory to execute the assay cases i.e. similar to login into the Zmail to executte this assay instance it is mandatory that login page of Zmail should last launched inwards browser. So the pre-requisite is Zmail page should last launched.
Test Steps: it is the steps to execute that assay cases.
Test Data: Test information is a information which is requires for that assay cases execution (also explained below).
Expected Output : way what output should organisation give if nosotros performs this assay cases on system.
Actual Output : Means later performing this steps on system, the organisation produced out is called actual output. If Actual output as well as Expected Output are dissimilar as well as thence it tin last said that the põrnikas is introduce inwards the system.
Status: status of the assay cases way top or fail, if actual as well as expected output matches alongside each other way assay instance passed else fail.
How to write the assay cases for the scenarios:
Lets reckon the scenarios written inwards above. Take a illustration of Inquiry shape the root scenarios is:
Scenario 1: Evaluate the Name patch of Inquiry form
- Check the minimum character.
- Check the minimum character.
- Check the answer when nosotros larn into digit inwards Name filed.
- Check the answer when nosotros larn into particular char inwards Name field.
- Check the answer when nosotros larn into Character inwards Name Field.
And much more…..
Scenario 2:Evaluate the Contact pose out filed of Inquiry form.
- Check if is direct hold the digit or not.
- Check past times entering xi digit.
- Check past times entering nine digit.
- Check past times entering char.
- Check past times entering symbols.
- Check past times keeping this filed empty.
And much more…
Like shown to a higher house y'all tin write the assay cases for every Scenarios.
Test Data:
The assay cases which nosotros are written to a higher house apparently requires about data, that information zero but Test Data.means the Data which is require to execute the assay cases is Test Data.it is real of import to collect proper data. Sometime customer give assay information to us. But many fourth dimension nosotros take away to exercise the assay data.
For illustration if out assay instance is like
Test Case : verify the login alongside valid credentials.
Test Date : User-name : Valid UID password : Valid PASS
Test case : verify the login functionality past times altering the user-name as well as password.
Test Data : User-name : Valid PASS password : Valid UID
Test case : verify the login functionality past times entering the particular symbols inwards it.
Test Data : User-name :String of particular characters (#$@#$ etc) password : String of particular characters (#$@#$ etc)
Test case : verify the question shape past times entering valid data.
Test Data :
- Name : XYZ
- Contact pose out : 95123*****
- Email : youremail@domainname.com
- Description : inquired most courses.
These are the few examples.