Software Testing Life Cycle

Software Testing Life Cycle process is an integral part of the Software Development Life Cycle. The overall aspect of STLC phase deals with testing and rectifying any error code generating within the program under various test conditions. STLC is simply a testing phase in the SDLC development. Validation and Authentication is tried and tested in this phase.

Specifies the various stages of testing:

STEP-1. REQUIREMENTS ANALYSIS

  • Study of SRS

STEP-2. TEST PLAN

  • Test Environment setup
  • Manual Testing planning
  • Defect Management planning

STEP-3. TEST DESIGN

  • Test Case preparation (By Developer and Tester both)
  • In case of enhancements, update the Test Cases
  • Test case reviews and Approval (Developer and Tester both)

STEP-4. TEST EXECUTION

  • Executing Test cases
  • Capture, Review and Analyse Test Results

STEP-5. DEFECT TRACKING

  • Find the defect & tracking for its closure

STEP-6. BUG REPORTING

  • Report the defect on ZOHO

STEP-7. Retesting of reported issues

STEP-8. Regression Testing

STEP-9. If build is fit for release then release the QA Certificate.

Client Feedback and re-development and re-testing if required (Repeat steps 2 to 9)

Client confirmation over module/project completion

Mobile Application

BUG LIFE CYCLE:

New: When a bug is found for the first time report it in bugzilla, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if that is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of ‘New’ is assigned to the bug.

Rejected: If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as ‘Rejected’.

Postponed: Sometimes, testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of Test data, unavailability of particular functionality etc. That time, the bug is marked with ‘Postponed’ status.

Deferred: In some cases a particular bug stands no importance and is needed to be avoided, that time it is marked with ‘Deferred’ status.

Contact Us