Test scenario and scenario testing

Posted By : Nitin Kumar | 28-Nov-2017

Test scenarios and scenario testing

 

Test scenarios are any functionality or set of test condition on which testing is to be performed.Test scenarios play a very important role in testing.Testers have to design the test scenarios by considering real world test condition so that testing can be done on that conditions with which good quality product can be delivered to the customer.

                                                                                                                                                                                     

 


 

Many people get confused in the test scenario and test cases.Test scenario and test cases are not same .Test scenario means "what is to be tested” and cases means “how is to be tested”.

 

Test scenario: Test the Registration page

 

Test cases: For registration page.

These are the conditions and steps on which the testing is to be performed.

1.Enter all the fields of registration page

2.Check the functionality by clicking on submit button

3.Enter the invalid credential

Test scenarios and test cases are very important.These are the backbone of testing.Testing should not start randomly by entered anything without awareness of what can be the result.But this thing is not completely wrong.Sometimes by entered any values randomly, some major bugs can be found out.you can take or understand it as”To hit something in dark”.


 

Scenarios testing

 

As we know “Exhaustive testing is not possible”.There are so many combinations and paths which is to be tested.But because of the dead line of project and cost factor exhaustive testing is not possible.Scenarios make the testing easy and also provides the base for the testing.

 

These are some pre-requisites for writing test scenario:

It is a important part.The preparation of test scenarios should be done after the consultation with the project manager, test manager, client, and developers.This makes easy for the testers to understand the actual requirement.

 

1.Testers should have knowledge and skills.

2.Testers should be able to understand the workflow of the project

3.Testers should have the functional and non-functional requirement.

4.Testers should understand the business logic.



Any misunderstanding of workflow and requirements leads the project to go in the wrong direction.

Related Tags

About Author

Author Image
Nitin Kumar

Nitin is a QA Engineer. He is adaptive and passionate to learn new technical skills.

Request for Proposal

Name is required

Comment is required

Sending message..