Software testing and its Process

Software testing is performed to verify that the completed software package

functions according to the expectations defined by the requirements/specifications.

SOFTWARE TESTING LIFE CYCLE

REQUIREMENT ANALYSIS PHASE:

 QA team prepares Requirement Traceability matrix (RTM) based on the

Software Specification Requirements Document (SRS).
 The RTM
RTM is used to record
record the relationship
relationship of the requirements to the design
(Test Cases).
 If any
any ambiguity found, it would
would be raised and cleared at this phase.

TEST PLANNING PHASE:

 QA Lead will prepare the Test Plan based on SRS document.

 It covers the scope of testing, test strategy, test environment, hardware and
software availability, resources, risks etc.
 Manager will review and then approve the test plan.
TEST CASE DEVELOPMENT PHASE:

 QA Lead distributes the work to the individual testers.

 Testers will start writing Test Cases based on SRS and Detailed Design
Document from the Development team.
 Test Cases are written using a standard Template or Automation Tool.
 Tester will send test cases for review to the QA Lead.
 Then the QA Lead will review and approve it.

TEST CASE EXECUTION PHASE:

  The Development team releases the software for testing along with their  Unit
Testing results and Release Notes.
 Then, the QA team performs Test Execution by executing the Test Cases,
which are already prepared.

TEST RESULTS and BUGS REPORTING PHASE:

 QA team provides the Test Summary report based on the test case

execution results.
 Bugs are reported in a Bug Report Template or Bug Tracking Tool.
 The Lead prioritizes the defects to be fixed based on the Bug Severity (1-
Critical, 2-High, 3-Medium and 4-Low).

DEFECTS RETESTING:

 QA team will submit the Bug Report after Cycle #1 testing is performed.
 Development team will release next build after all the bugs are fixed.
 In the Cycle#2 testing, QA will test whether all the bugs reported in Cycle#1
are fixed or not.

REGRESSION TESTING:

 QA will run the Regression test cases to make sure all the functionalities are
working as expected after the code change for the bug fixing.
 The same process is repeated till the Delivery Date.

TEST CLOSURE:

 At the time of release there should not be any high severity and high priority
bugs.
 It may have some minor bugs, which are going to be fixed in next iteration or
release (generally called deferred bugs).
 At the end of Software Delivery, QA Lead and individual testers prepare test
reports.
 Testing team is also responsible to keep the track of Change management
and Version Control of the software to give qualitative product.
 The process review meetings need to be done and lessons learned should be
documented. A document is prepared to cope up similar problems in future
releases.

Defect Lifecycle

 A defect is logged in OPEN state in the bug tracking tool when the tester finds
any variation in the test results during testing. After this an e -mail is generated
and sent to the Development Lead or Manager.

 Then the Development Lead analyzes whether it is a valid bug. If so, he will
assign to the respective developer to fix it. The defect state is changed to
ASSIGNED and email notification sent to the respective developer.

 Once the defect is assigned to the developer it is fixed by developer and

changed to FIXED state. After this an e-mail is sent to the QA who reported
the defect to verify the fix.

 The tester verifies the fix and closes the defect, after this defect moves to
CLOSED state.

 If the defect fix does not solve the issue reported by QA, then the QA re-
opens the defect and defect moves to RE-OPEN state.

 Then the manager analyzes whether it is a valid re-open and if so, he assigns
back to the respective developer and the issue stat e is changed to
ASSIGNED and an email is sent to the developer.
 If the issue reported by QA is not an issue, manager will reject the bug. The
issue state will be changed to REJECTED and an email notification
will be sent to QA for the same.

 If the issue fixing can be postponed for future release, manager defers the
issue. The issue state will be changed to DEFERRED and an email
notification will be sent to QA for the same.