Skip to main content

Identifying test scenarios

Identifying Test Scenarios


Test scenarios:
Test scenarios are the high level classification of test requirement grouped depending on the functionality of a module.


Test case: 
Test cases for software help guild the tester through a sequence of steps to validate whether a software application is free of bugs and working as required by the end user. 
A test case with valid functionality is called positive test case and a test case with invalid functionality is called negative test case. Test case should cover most of the positive inputs and should be developed for all most common potential scenarios.
The basic objective of writing test case is to validate the testing coverage of the application.
A good test case should have high priority of finding bugs.




Test Case Template: 
  • Test scenario ID - The ID of the test suite to which this test case belongs.
  • Test case ID - The ID of the test case.
  • Category - The type of the test case. 
  • Feature description - The objective of the test case.
  • Prerequisites - Any precondition that must be fulfilled prior to executing the test.
  • Test description - Step by step procedure to execute the test.
  • Input Data - The test data or links to the test data, that are to be used while conducting the test.
  • Expected result - The expected result of the test.
  • Severity - The impact of the bug on the application.
  • Actual result - The actual result of the test is to be filled after executing the test.

Test case for login page:

First we should go through the SRS or BRS and identify the test requirements.
  1. User name should have alphabetic characters, numeric characters and periods.
  2. User name should not be left blank.
  3. User name should not be more than 40 characters.
  4. User name should not start with or contains any special characters.
  5. Password should have at least 6 characters.
  6. Password should have contains alphabetic characters, numeric characters and special characters.
  7. Password should not contain spaces and periods.
  8. Password should not be more than 40 characters.
Then we should identify the test scenarios.
Test scenarios for the login.
The validation table for the login.
When writing test cases, the following documents are referred.
1. Business requirement document
2. Software requirement document
3. Functional specification
4. Use cases 
5. Test designs
6. Previous releases 
7. User manual and help  

Thank you,
Dananji.

Comments

  1. TharushiNovember 8, 2016 at 10:58 PM

    Fantastic Article on Testing.. Waiting for more Articles

    ReplyDelete
  2. arshiya fouziaJanuary 4, 2021 at 2:44 AM

    Awesome post, Thanks for sharing nice information. It's really more than effective for us..
    software testing course

    ReplyDelete

Post a Comment

Popular posts from this blog

Strategies and methods for test case design II

Strategies and methods for test case design Today we are talking about how to get an approach for writing a good test case. Developers cannot prevent or eliminate all the defects raised in the application during implementation. That's why the application should be tested before deliver to the customer. Before starting the execution, we need to identify test scenarios and write test cases for each identified scenarios. Test case is test description which needs to be executed to verify the functionality or feature of the application. A good test case have a good possibility of finding defects. For designing effective test cases, there are two basic strategies that can be used. Black box test strategies White box test strategies Test Strategies Sources Testing Techniques Black Box  Functional requirement specification Equivalence partitioning   Business requirement specification Boundary value analysis   Domain knowledge State Transition Testing     ...
Post a Comment
Read more

Java basic for Selenium - Selenium Tutorial II

Today we are talking about Array. The software tester should have some basic knowledge about java when writing selenium scripts for the validations. Array is a data structure where stored in elements in same data type. The declaration and initialization an array as follows. int[]  Array_a;   or  int  Array_a[]; - This is an integer array. int[10] = Array_num;  - This is an integer array which stores 10 elements. Array_num[0] = 10;    - Assign value 10 to 0 th element of array. (Index [0]) int[]   Array_num = { 1, 2, 3, 4, 5 };  Finding maximum value of an array Finding minimum value of an array Finding average value of an array Find the key of an array Reverse an array The time complexity of this algorithm is   O(n/2)   which is O(N) because we are iterating over array till midpoint only. The initial iteration is happening as follows The...
1 comment
Read more

Strategies and methods for test case design I - Requirement traceability matrix

Requirement traceability matrix Today we are talking how to design requirement traceability matrix for Amazon web page. This is the URL for Amazon  https://www.amazon.com The process for designing requirement traceability matrix is as follows. Identifying business requirement Identifying functional requirement Identifying test scenarios Identifying test cases for each scenarios Finding validation tables for related test cases Identifying business requirement Business requirements are performed for meeting organizational objectives and finding solutions. Business requirement specification is designed by business analyst. The main objective of this document is to find out business solutions for the identified problems. It is covered customer needs and expectation. Use cases are designed after being gathered and validated business requirements. Identifying functional requirement Functional requirement specification is designed as a formal statement of application’s funct...
1 comment
Read more