Manual Testing Material

Bug tracking is a process in which the defects are identifying, isolated and managed.

Defect Profile Document
Defect ID:
The sequences of defect numbers are listed out here in this section.

Steps of Reproducibility:
The list of all the steps that are followed by a test engineer to identity the defect are listed out here in this section.

Submitter:
The test engineer name who submits the defect will be mentioned here in this section.

Date of Submission:
The date on which the defects submitted is mentioned here in this section.

Version Number:
The corresponding version number is mentioned here in this section.

Build Number:
Corresponding build number is mentioned here is this section.

Assigned to:
The project lead or development lead will mentioned the corresponding developers name for name the defect is assigned.

Severity:
How serious the defect is, is described in terms of severity. It is classified in to 4 types.

1. FATAL :Sev1 S1 1
2. MAJOR :Sev2 S2 2
3. MINOR :Sev3 S3 3
4. SUGGESION :Sev4 S4 4

FATAL:

It is all the problems are related to navigational blocks or unavailability of functionality then such types of problems are treated to be FATAL defect.

Note: It is also called as show stopper defects.

MAJOR:

It at all the problems are related to the working of the features then such types of problems are treated to be MAJOR defects.

MINOR:

It at all the problems are related to the look and feel of the application then such types of problems are treated to be MINOR defects.

SUGGITIONS:

If at all the problems are related to the value of the application then such types of problems are treated to be suggestions.

Priority:

The sequence in which the defects have to be rectified is described in terms of priority. It is classified in to 4 types.

1.CRITICAL
2.HIGH
3.MEDIUM
4.LOW

Usually the FATAL defects are given CRITICAL priority, MAJOR defects are given HIGH priority, MINOR defects are given MEDIUM priority and SUGGITION defects are given LOW priority sent depending upon the situation the priority may be changed by the project lead or development lead.

Ex: -

Low Severity High Priority Case:
In the case of customer visit all the look and feel defects, which are usually less savior, are given highest priority.

High Severity Low Priority Case:
If at all some part of the application is not available because it is under development still the test engineer will treat team as FATAL defect, but the development lead will give less priority for those defects.

BUG LIFE CYCLE :


1.New / Open:

When ever the defect is found for the first time the test engineer will set the status as New / Open. But some companies will say to set the status as only new at this situation and once the developers accept the defect they will set the status as open.

2.Reopen and Closed:

Once the defects are rectified by the developer and the next build is released to the testing department then the testers will check whether the defects are rectified properly or not.

If they feel rectified they will set the status as Closed. Other wise they will set the status as Reopen

3.Fixed for Verification / Fixed / Rectified:

When ever the test engineer raises the defects, accepted in the developers. Rectified then they will set the status as Fixed.

Hold:
Whenever the developer confused to accept or Reject the defect he will set the status as hold.

Testers Mistake / Testers Error / Rejected:
Whenever the developer is confused it is not at all a defect then he will set the status as reject.

As Per Design (This is a Rare case)
When ever some new changes are incorporated engineers then the test engineers will raze then as defects but the developers will set the status as ‘As Per Design’.
Error:
It is a problem related to the program.

Defect:
If the test engineer with respect to the functionality identifies a problem then it is called defect.

Bug:
If the developer accepts the defect, that is called as Bug.

Fault / Failure:
The customer identity the problem, after delivery. It is called Fault / Failure.

In this phase the test engineer will compare the expected value with actual value and mention the result as pass if both are match other wise mentioned the result as fail.

Types of Test Cases
Test cases are broadly divided into two types.

G.U.I Test Cases.
Functional test cases.
Functional test cases are further divided into two types.

Positive Test Cases.
Negative Test Cases.
Guidelines to prepare GUI Test Cases:

1.Check for the availability of all the objects.
2.Check for the alignments of the objects if at all customer has specified the requirements.
3.Check for the consistence of the all the objects.
4.Check for the Spelling and Grammar.
5.Apart from these guidelines anything we test with out performing any action will fall under GUI test cases.

Guidelines for developing Positive Test Cases.

1.A test engineer must have positive mind setup.
2.A test engineer should consider the positive flow of the application.
3.A test engineer should use the valid input from the point of functionality.

Guidelines for developing the Negative Test Cases:

1.A test engineer must have negative mind setup.
2.He should consider the negative flow of the application.
3.He should use at least one invalid input for a set of data.

Test Case Template:

Test Objective :
Test Scenario :
Test Procedure :
Test Data :
Test Cases :


1.Test Objective:
The purpose of the document is clearly described here in this section.

2.Test Scenarios:
The list of all the situations that are to be tested, that are listed out here in this section.

3.Test Procedure:
Test procedure is a functional level term, which describe how to test the functionality. So in this section one will describe the plan for testing the functionality.

4.Test Data:
The data that is required for testing is made available here in this section.

5.Test Cases:
The list of all the detailed test cases is- listed out here in this section.

Note:

Some companies even maintain all the above five fields individually for each and every scenario. But some companies maintain commonly for all the scenarios.