Software Testing Life Cycle (STLC) in Software Testing

Development is indeed the most important part for any company; however software testing services are essential to keep the software going and stay ahead in the long run. Software testing process is vital in software development life cycle. The process deals with testing and verifying the errors generated within the program or code under various test conditions. Also this phase deals with validation and authentication. Cryptex offers customized testing services for its clients. The qualified professionals at Cryptex conduct the application testing and look for the client needs as per the various parameters. Safety and security of the client’s application is of paramount concern at the Cryptex. Putting the web application through various stages of testing using both automated testing and manual testing, takes the client through trusted journey of the application.

Specifies the various stages of testing for software quality assurance:


  • Study of SRS


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


  • 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)


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


  • Find the defect & tracking for its closure


  • 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

The reason behind software testing is a bug.

When a bug is discovered for the very first time, it is reported in the bugzilla. A tester then communicates it to the team leader and it is verified whether the bug is valid or not. After the confirmation it is assigned the status of a ‘new’ bug.

If the bug is found to be invalid and the software functions smoothly, the bug is assigned the status as, ‘rejected’.

In case the testing of bug is postponed for an indefinite time period, due to numerous valid reasons, the bug is assigned the status as, ‘postponed’.

Lastly, if the bug is irrelevant and needs to be avoided, it is assigned the status as, ‘deferred’.