How to write test cases effectively:

In this post we discuss the below point:

1. Why we need to make a test case sheet

2. which format can use to make effective and attractive

1. Why need to make test case sheet:

      before we start the main topic let's first discuss about why we need, and this questions ask in an interview also so let's discuss...

1. first and for the most reason behind that less time consuming to testing software:

     I am saying this because we made test cases before the developer has done programming. Basically, all testers made test cases is based on the requirement documents. once the developer done software then directly doing test software.it takes less time to test and fastly. 

   

2. If some tester taking leave or change company:

     the second reason is sometimes employees take a leave and project deadlines are too nearer then the manager should give a testing project to another tester. If before the first tester made test cases then it's easy to understand, requirements and can don testing fastly before end of the deadlines.

3. Third reason is in testing field s many project testing at a time so after bug resolved tester has to retest so some time developer takes much time to resolved bug and send to tester after week/month.at this time of tester have a test case sheet then he/she easily adopt previous task and don retest fastly.

2. How to make an effective test case sheet:

       The below link is for the test case sheet template:

      Test case template with example

Now let's discuss the test case sheet regarding:

Module / Functionality Name	Telegram Integration in xyz software
Reference Document Path
Created By	XYZ
Created Date	9/17/2020
Review Date

1. Module/functionality name: in this field tester should have written which module or particular functionality to test

   For ex. here we test telegram functionality so write: Telegram functionality in xyz software

2. Reference document path: in this field we mention the requirement document path, with the help of which the tester created.

3. created by here mention name of tester which made a test case 

4.craeted date: mention the date of that day.

5. review date: this is to write date of the day that our mentor reviewed it

Test Scenario ID :	TS_01
Test Scenario Description	Check Login Functionality

#Pre condition :

   in the mention of this field all pre-requirement

   For ex. we login into the web for telegram login pre-conditions are:

       1. open URL:

       2. Site should be up and run

       3. Log in the valid credential(if tester here not mention then he can mention in the test data field)

1. Test scenario ID: 

 Test scenario means one module in this module multiple test cases

  For ex. the login module is the test case scenario in this scenario can make multiple test cases 

  for ex. (i) valid user name and password

              (ii) invalid user name and password

              (iii) valid user name and invalid password

              (iv)  invalid user name and valid password 

above for are test cases. So it means that one scenario can be multiple test cases.

2. Test scenario description: description of the scenario

Test Case Id

Test Case Description

Test Steps

Test Data

Priority

Expected Result

Actual Result

Test Status

Remark

1. Test case id: 

mention unique id 

 For ex. TS01_LOG_001

       Here TS01 means test scenario 1, LOG means login. and 001 means first test cases tester can enter by own choice but most preferable if enter like this above mention.

2. Test case description: 

    in this field explain which we want to check

    For ex.  to check login functionality with valid mobile no

3. test steps:

    This is so important part so mention all the steps  tp generate this test case

     For ex. user login in telegram check in app so steps are like below:

           1. Install the application

           2. click on login/sign in

           3. enter mobile no

           4. Click on the login button

           5. Enter OTP which we got in via message

           6. click on ok

4. Test data: 

     this fields are using when we have to mention data 

     for ex. in login we have to mention which credential are use

           user name/mobile no/mail is:

           password:

5. Priority : 

     It is the most important field in testing.

     Basically three types of priority:

         1. High

         2. Medium

         3. Low

       According to the test case mention priority

6. Expected result : 

     In this fields, the tester writes what expect the result

     For ex. in login functionality expected result is:

            - it should be logged in successfully

7. Actual result: 

     In this fields what we actually getting by testing this

     For ex. if login successfully then write: same as expected

                 if login is not successful then write: here getting error in login

8. Test status:

     in this fields mention this test case PASS or FAIL.

     if the actual result same as expected then mention PASS

     if the actual result not the same as expected then mention FAIL

9. Remark: 

    if some remark then you can mention here

To know the difference between functional and integration testing click on the below link

Difference between functional & integrational testing