Test Scenarios vs Test Cases
Test Scenario:
An item of a element or System that could hold upward verified past times i or to a greater extent than Test Cases. It is too called equally Test Condition.
Test Case:
Execution preconditions & post-conditions, input data, expected result, developed for a item exam status inward gild to verify compliance amongst a specific requirement.
Example for Test Scenarios too Test Cases
We bring different Types of Test Requirements, Example,
Functional Test Requirement
Performance Test Requirement
Usability Test Requirement etc....
I am taking Functional Test Requirement,
-------------------------------------------------------
Functional Test Requirement: Login to Application using valid input
Test Scenarios
Test Scenario 1: Login to Application using valid Username too Password (Positive scenario)
Test Scenario 2: Invalid Login endeavour (Negative Scenario)
Test Cases
Test Scenario 1: Login to Application using valid Username too Password (Positive scenario)
Test Case: Login to Application amongst valid Username too Valid Password
Test Data:
User Name = admin
Password = admin@123
---------------------------------------------
Test Scenario 2: Invalid Login endeavour (Negative Scenario)
Test Case 1: Login to Application using Valid Username too Invalid Password
Test Data:
User Name = admin
Password = abcd123
Test Case 2: Login to Application using Invalid Username too Valid Password
Test Data:
User Name = Hyderabad
Password = admin@123
Test Case 3: Login to Application using Invalid Username too Invalid Password
Test Data:
User Name = Hyderabad
Password = xyz1234
etc....
-----------------------------------------------------------
Note:
One Test Scenario may bring i or to a greater extent than Test Cases, usually unmarried Test Case is enough for Positive Test Scenarios, but multiple Test cases are required to embrace Negative Test Scenarios.
In this document I wrote only Test Case names only, you lot write Test cases amongst all required fields, Test Case Template may vary from i society to roughly other but piece of job is same,
Regular fields inward Test Cases,
Test Case ID:
Test Case Name / Description:
Precondition:
Post Condition:
Steps to Execute:
Expected Result:
Test Result:
---------------------------------------------------
Login Page URL: www.gcrit.com/build3/admin/
Username: admin
Password: admin@123
---------------------------------------------------------------
Test Scenario:
An item of a element or System that could hold upward verified past times i or to a greater extent than Test Cases. It is too called equally Test Condition.
Test Case:
Execution preconditions & post-conditions, input data, expected result, developed for a item exam status inward gild to verify compliance amongst a specific requirement.
Example for Test Scenarios too Test Cases
We bring different Types of Test Requirements, Example,
Functional Test Requirement
Performance Test Requirement
Usability Test Requirement etc....
I am taking Functional Test Requirement,
-------------------------------------------------------
Functional Test Requirement: Login to Application using valid input
Test Scenarios
Test Scenario 1: Login to Application using valid Username too Password (Positive scenario)
Test Scenario 2: Invalid Login endeavour (Negative Scenario)
Test Cases
Test Scenario 1: Login to Application using valid Username too Password (Positive scenario)
Test Case: Login to Application amongst valid Username too Valid Password
Test Data:
User Name = admin
Password = admin@123
---------------------------------------------
Test Scenario 2: Invalid Login endeavour (Negative Scenario)
Test Case 1: Login to Application using Valid Username too Invalid Password
Test Data:
User Name = admin
Password = abcd123
Test Case 2: Login to Application using Invalid Username too Valid Password
Test Data:
User Name = Hyderabad
Password = admin@123
Test Case 3: Login to Application using Invalid Username too Invalid Password
Test Data:
User Name = Hyderabad
Password = xyz1234
etc....
-----------------------------------------------------------
Note:
One Test Scenario may bring i or to a greater extent than Test Cases, usually unmarried Test Case is enough for Positive Test Scenarios, but multiple Test cases are required to embrace Negative Test Scenarios.
In this document I wrote only Test Case names only, you lot write Test cases amongst all required fields, Test Case Template may vary from i society to roughly other but piece of job is same,
Regular fields inward Test Cases,
Test Case ID:
Test Case Name / Description:
Precondition:
Post Condition:
Steps to Execute:
Expected Result:
Test Result:
---------------------------------------------------
Login Page URL: www.gcrit.com/build3/admin/
Username: admin
Password: admin@123
---------------------------------------------------------------