Home Java Overview Maven Tutorials

Sunday 22 January 2017

TEST CASE, TEST PLAN and RTM(Requirement Tractability Matrix)

How to write the test cases?
Test cases are written based on documents(adopted by the organization) like Business Requirement Specification(BRS) , Functional Specification(FS) or any other document which functionally describe the application.
It is good practice to write the test cases in early phase of development.
An ideal Test cases cover three section
  1. History of Test cases (Written by, Reviewed by, Approved by).

  2. Scenarios

  3. Scenario description & steps to achieve that scenario.

And the possible result of scenario/test steps execution can be : PASS, FAIL & PENDING(Due to defect, due to environment, Due to query etc.)
When to start test case execution ?
Execution of test cases can be started after successful completion of Smoke test.
Key Points :
  1. Every Test cases must be discrete.

  2. Test cases must be tune with the flow of application & should be in simple language.

  3. Test case should cover most of the functionality.

Test Case Design technique :
1. Test cases can be derived directly from a requirement specification or black box test design technique. These techniques are :
> Boundary Value Analysis
> Equivalence Partitioning
> Decision Table Testing
> State Transition Diagrams
> Use case Testing

2. Test case can also be derived from structure of System These techniques are :
> Statement Coverage
> Branch coverage
> Path Coverage
> LCSAJ Testing
3. Test cases can also be derived from tester experience on similar systems These techniques are :
> Error Guessing
> Exploratory Testing
Equivalence class partitioning :  Divide all possible inputs into classes (partitions) such that
                                                         • There is a finite number of input equivalence classes
                                                         • You may reasonably assume that
                                                                     • The program behaves analogously for inputs in the same class
                                                                     • A test with a representative value from a class is sufficient
                                                                     • if representative detects fault then other class members will detect the                                                                        same fault Below is an example with test case for Equivalence when a finance account will accept age only for 18-40  :
Test case :
SR Objective Steps Test data Expected Actual Status
1 Verify the age input box functionality input the numeric value in Age input box 0 to 18 Message " You are not eligible to open the account"
Input the invalid numeric value in input box(optional) -1 Message "Please enter valid data"
Input the valid numeric value in input box 18-40 green confirmation message should appear
input the value in numeric to input box More than 40 Message "You can not apply to open account"
Boundary Value Analysis : In any application it is most likely common that error occurs at boundaries.
                                                 Testing boundary conditions of eq. classes is more effective
                                                 i.e. values directly on, above, and beneath edges of eq. classes
                                                 • Choose input boundary values as tests in input eq. classes
                                                    instead of, or additional to arbitrary values
                                                 • Choose also inputs that invoke
                                                    output boundary values
                                                   ( values on the boundary of output classes ) Below is an example of test case for Boundary value :
SR Objective Steps Test data Expected Actual Status
1 Verify the age input box functionality input the numeric value in Age input box -1 Message "Please enter valid data"
Input the invalid numeric value in input box 0 Message " You are not eligible to open the account"
Input the valid numeric value in input box 17 Message " You are not eligible to open the account"
input the value in numeric to input box 18 green confirmation message should appear
input the numeric value in Age input box 19 green confirmation message should appear
input the numeric value in Age input box 40 green confirmation message should appear
input the numeric value in Age input box 41 Message "You can not apply to open account"

Decision Table Testing :

if different combinations of inputs result in different actions then it is difficult to to show using equivalence partitioning and boundary value analysis.
Example :  If an web page have two input box A & B where A is mandatory & if A or both are enable than only submit button will enable :
Condition                                                                                 Rule 1                                    Rule 2                       Rule 3
Input box A    (Mandatory)                                                            F                                             T                          F
input box B                                                                                      F                                             F                           T
Expected : Submit button                                                             F                                             T                           F

Use case testing technique :  Test case can also be derived from usecase documents . 

Test Management tools:
  1. QTest

  2. PractiTest


  4. Test collab

  5. Xqual

  6. Test Rail

  7. Test Lodge

  8. Jira (Also a bug tracking tool)

  9. IBM Rational Quality Manager

  10. HP Quality Center


Test Plan

A Test plan is a document which is very similar to project plan but mainly focusing on testing which would be done.
It have the various section inside it, which explain how, when & what should be tested in a particular project.
It varies from organization to organization & project to Project.

The effectiveness of testing depends on robustness of test plan.

Test Plan Definition :A Software test Plan is a document that describes testing activities, scope, strategy, testing tools, Environment etc
ISTQB Definition: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice,and any risks requiring contingency planning. It is a record of the test planning process.

Test Plan TYPES :
Test plan can be divided into three major categories :
Master Test Plan : This test plan set a bench mark or parameter how other test plan should be created.
Testing Level Specific Test Plan : Like Unit testing Test Plan, Integration Testing Test Plan etc.
Testing Types specific Test Plan: Like Penetration Testing Test Plan, Security Testing Test Plan etc.
Here i have uploaded a sample TEST Plan Which can be downloaded by click the below link.
This sample test plan cover almost features of a test plan.

Click here to download sample of Test Plan

Tags :What is Test Plan?,What are main components of test plan?, how to create test plan?, Download Sample test plan

RTM : RTM stands for REQUIREMENT TRACEBILITY MATRIX and it is a document which Map functionalities to test cases.

Key Points :
>> In General, Rows have functionalities & column have Test case ID.
>> It ensure that each functionality have been covered in test cases.
>> When a Requirement will change then Associated test case will change & Changes can be traced easily.
>> Its life start with the project & and ends with the project.

Tags :-

What is test plan?

How to create test plan?

What is RTM?

Download sample test plan

Example of RTM

What are test cases?

How to design test cases?

No comments:

Post a Comment