What is Simpplr's QA Process?

Table of contents

Overview

Development phase

Quality Assurance (QA) phase

Release phase

Overview

Our release process is structured around two sprint cycles, focusing on the development of new features, bug resolution and improvements, as well as a detailed Quality Assurance (QA) process. This document outlines the steps involved from development through QA testing to the final production release.

Development phase

Daily regression and sanity testing on test environment

• Frequency: Daily! We conduct automated regression test for each function on daily basis after daily code deployment on TEST environments
• Tests Include:
  • Regression testing: To ensure new changes haven't adversely affected existing functionalities
  • Sanity testing: Quick, surface-level testing to verify that functionalities work as expected and there are no blocker or critical issues

Code freeze

• When: At the end of sprint 2 cycle
• Purpose: To stabilize the codebase for final testing and code deployed to QA (Staging) environment

Quality Assurance (QA) phase

Move code to QA environment

• Process: Post code freeze, the stabilized codebase is moved to the QA environment for in-depth testing
• Objective: Validate the application in an environment that closely mirrors production

Regression and sanity testing on QA environment

• Activities: Comprehensive regression and sanity testing to ensure the application meets quality standards
• Outcome: Confirmation that the application is ready for production

Release phase

Final decision

• Criteria: Success in all QA tests
• Decision Points:
  • Success: Proceed to production release
  • Failure: Return to the development phase for necessary adjustments

Release to production

• Process: Upon successful QA sign off, the application is released to the production environment
• Objective: New features and fixes are available to use