Roles and Responsibilities Of Software Tester: Agile, Requirement analysis,test scenario,test case,test data

Role and Responsibilities Of Testers

Role and responsibilities of tester: tutorial

Introduction

In this tutorial we try to complete the all important points regarding to software tester role and responsibility.

This tutorial help you to clear understanding of the what is important and major role and responsibilities of tester in agile.

Roles and Responsibilities Of Software Tester As Following

Roles and Responsibilities Of Software Tester

1.Requirement analysis

Requirement analysis is important and first role which play by testers in Agile  Methodologies after receiving the test plane from test lead tester start to first understand the requirements what actual client wants?what are the requirements?

This All requirements BA collect from client and prepare documents BRS and SRS.If tester not understand the requirement clearly then the issue is come in next will he actual start to test without understand the requirement tester not to go to next step and it is good approach of tester.

If tester having clear about the requirement of functionality on which tester should work then tester having easy to do test scenario and test cases design.

2.Creating Test scenarios

After understanding the requirement tester start to write the test scenario .Test scenario is basically a high level document which contains of all the possible way of testing the application 

Here tester should try to break the application in multiple way and prepare positive & negative scenario to better understanding of application functionality in both ways positive as well as negative condition.

Positive scenario means to check the application with valid input data and 

Negative scenario means check the application with invalid input data and see the how application respond in invalid case and what is impacted output.

Here tester should first understand the requirement of given functionality and then start to creating test scenarios on for that tester should break the application and try to right the test scenarios in both positive and negative ways this test scenario help to understand the  functionality of application and also it helps to creating test cases.

Important point in test scenario is tester should cover the each and every features of application if any important functionality is missing when creating a test scenarios it will impact on the application functionality and in feature bug is raise.

3.Test  case Design

After the creating test scenario tester start to write the test case design on the bases of test scenario here test case design consist of the navigational statements contains means input data,expected output,defect if raise,test case steps,actual result,test result pass/fail,and review tester mention in the test case design.

Test case design is the detailing of test scenario in the test case design "How to test the application" explain the functionality of application in terms of steps.Test cases are derived from the test scenario which written/prepared by the Test Engineer.

Following are the some points of test case design template

1.Test case ID

In test case ID is the ID of that specific test case which we have to test.

Example -If test case is first then Test case ID is TC_001

2.Test scenario

In test scenario mention what we have to test.

3.Test case priority

 

In this test case priority column mention that specific test case or test scenario priority in high or low categories

That means on the basis of this priority give the preference of that test case first.

4.Prerequisites

Prerequisites means what we have with us when we before we start the testing.

Example-Link or URL of that product to be check.

5.Test data

Test data means the data which requires before the testing which contains positive and negative test data.

6.Test case steps

 

Test case steps which contains the navigational steps or we can say how to test the application step by step 

7.Expected results

Expected result means what client wants it means it mention customer or client requirement.

8.Actual result

After testing what actual result come out is mention in actual result 

9.Test result

Test result means after test case execution that specific functionality or test case is pass or fails

10.Test case Run/Not Run

Test case or that specific functionality of application is run or not run.

11.Defect ID

At the time testing if defect is raise then we mention that specific defect in defect ID column

12.Review

How review the case that name is mention here.

Here all the above point template is nearly same but sometimes its depend on company also it just give you some idea to understand the test case design 

4.Creating Test Data

Test data is and important point test data is basically a document/input data used to test the software programs/applications.it helps to test the application and also required to the testing/test case execution.

Test data is explain in 2 categories

1.Positive Test data

Here positive test data is generally creating to give the positive test data/input to system and find out the expected result.

2.Negative test data

Here negative test data is generally creating to give the negative test data/input to system and find out the unexpected result or the unhandled conditions.

5.Traceability Matrix

Traceability matrix is important term to software testers. In Traceability matrix tester  identified the missing test cases and also add that missing test cases to better performance of the application.

"Traceability matrix is define as the it is mapping between business requirement and written test cases".

In actual software tester prepare a traceability matrix where if tester found any missing test case then tester should add it in traceability matrix.

Traceability matrix is used to find out missing test cases also in traceability matrix all review test cases are check the again and again and find out the missing test cases and add in traceability matrix.

Two way to prepare Traceability Matrix Use the following tools 

1) Excel sheet

In some industries use the excel sheet to prepare Traceability matrix.To prepare the Traceability matrix which tool is used is all depend on the industries which teste works.

2)HP-ALM (Project Management or Defect Management Tool).

In some industries use the HP-ALM Tool to prepare Traceability matrix this tool is advance and save the time.

Following are the two types of traceability matrix

1) Forward Traceability Matrix.

2)Backward Traceability Matrix.

  

To learn about more the traceability matrix visit :-Software testing life cycle (STLC)

6.Test case execution

After receiving the build from developer tester start to execute the test cases one by one During execution tester perform the first is smoke testing.

1.Smoke testing

As soon as tester should receive the build from developer tester start the testing with smoke testing first.Smoke testing means to test the application.Here tester test the build is stable or not.

Where tester enter the URL and launch the application and check actual link validation,URL validation,page validation,tan validation.

Also tester check the GUI(Graphical user interface) check the features like color,font,buttons,all important tabs are present are not etc.

Smoke testing is the part of basic testing its also called Zero Level Testing.

2.Sanity testing

After the smoke testing tester sanity testing is done by testers where tester test the main functionality of the application without going into the deeper.

Example:-Suppose there is application and there present recharge functionality tab so we just click on the recharge button/tab and check its work fine or not without checking its internal functionality.

 NOTE:-Smoke and Sanity is also called as Zero Level Testing.

3.Functional Testing

In functional testing means "How will system perform".tester test the application to identified the results/see the result is as per customer expectations or not.In BRS /SRS document all requirement in mention.

Following are the functional testing tester need to perform

1.Behavioral testing

2.Input domain testing

3.Error handling testing

4.Back end database testing

5.Service level testing

6.Calculation based testing

4.Non-Functional testing

Non functional testing tester check the behavior of the application in short tester need to test the "How well system/application responds".

In non functional testing tester test the application response time.

Following are the Non-Functional testing tester need to perform

1.Recovery testing

2.Compatibility testing

3.Configuration testing

4.Installation testing

5.Intersystem testing

6.Sanitation testing

7.Parallel testing

8.Globalization testing

5. Retesting

During test case execution process tester found any defect then he raise as defect to his assign developer after that developer fix that defect and send modified build to tester.

On that modified build tester start doing retesting and regression testing.

In retesting test engineer going to check whether bug or defect is fix or not.

During resting tester check the modified build which send by developer after fixing the bug.

In retesting test engineer is going to concentrate on specific particular functionality where actual bug is occured.

6.Regression Testing

"Whenever their is new functionality is added and whenever there is defect fix then in both this cases there is change in code by developer due to that change in code tester need to check its not effect on existing functionality"

In two condition tester should perform regression testing whenever there is new functionality is added and whenever there is defect fix.

Two times tester need to perform regression testing 

1.Every new build.

2.second is master build.

Following are two types of Regression testing

1) Regional type regression testing

2) Full regression regression testing

Note-To learn about more the traceability matrix visit :-Software testing life cycle (STLC)

7.Defect Logging

During the test case execution if any defect is found then tester raise a defect and logging that defect to the concern developer.Tester log the defect by using defect management tool JIRA or HP-ALM.

8.Client interaction/Demo

After the all testing activates done tester should give demo to client and show the application/functionality is working fine as per his expectations.

This happen in sprint review meeting.Here tester is directly interact with the client. 

Important Questions Related To Interview/Exam.

1.What is test summary report who prepared the test summary report?

→Test summary report/software release note it contains final summary of all the testing activities done in hole process and how testing is done.

Test lead prepared the test summary report 

Test summary report consist.

1)Total number of test cases executed

2)Total number of fail test cases.

3)Overall fail percentage

4)Approved by.

5)Defect/deviation problem.

6)Comment if any.

7)Total number of pass test cases

8)Overall pass percentage.

Note-To learn about more the traceability matrix visit :-Software testing life cycle (STLC)

2.Full form of GUI

→Graphical user interface

3.Which testing called zero level testing?

→Smoke and Sanity called Zero Level Testing.

4.Why we need negative testing?

→ We need negative testing to ensure the software application do not crash and remains stable with data inputs.

5.Rules to write test scenarios?

→1.Test scenarios should be simple and not more than the 2 to 3 lines because it is and one line statement

2.Test scenarios should written end to end.

6.In test scenario identification which parameters we should considers?

→1.GUI parameters

    2.Functionality related parameters

    3.Database related parameters

    4.Business logic related parameters

7.What is test data?

→ Test data is input data for testing which contains positive and negative test data.

8.What is logn form of URL?

→ Uniform Resource Locator.