The Three Phases of the Deployment Testing Cycle

Testing a software project before and after deploying it on production is not that difficult. But too often, major bugs appear on production server after the deployment process. To avoid situations in which your production environment is threatened by these bugs, you should use a streamlined deployment and testing flow.

Generally speaking, this flow consists of three phases: pre-deploy, deploy and post-deploy.

During the Pre-Deploy testing phase, both the development team and the QA engineer should be tasked with the following items:

  1. Ask developers to copy database from Production to Stage.
  2. Announce a Code Freeze for the entire development team.
  3. Retest new features and bug fixes.
  4. Perform general smoke testing using checklists.
  5. Report all bugs, categorizing them with a consistent metric for urgency.
  6. Test urgent bug fixes and engage in regression testing of this functionality.
  7. When Stage is tested and has no major and/or minor bugs (depending on the project), — announce deployment.

When the QA engineer announces the Code Freeze, developers cannot push, commit, or deploy anything. But they can still continue working on their local environment, so no time is wasted. When the Code Freeze is cancelled, developers can push, commit, and deploy their work to Stage.

After finishing the pre-deploy testing cycle, the manager has to approve the deploy process before the developer who is responsible for this process puts it into motion. Having one developer be responsible for deploys is always beneficial, as it avoids misunderstandings like incorrectly merged branches.

After the deployment is done, QA begins the Post-Deploy phase, which consists of the following tasks:

  1. Perform general smoke testing using checklists.
  2. Report all bugs, categorizing them with a consistent metric for urgency.
  3. Urgent bug fixes should first be deployed on the Stage environment. Here, QA can test them, and engage in regression testing before deploying them on production. Then, the testing cycle — including bug fix testing and regression testing — should be repeated.
  4. When production is tested and has no issues, — deployment is complete.
  5. Cancel Code Freeze, or wait for client feedback as needed before cancelling Code Freeze.

If for any reason issues appear during the deployment process, you should quickly troubleshoot them. Here are some examples of possible problems and their solutions:

  1. If developers violated Code Freeze, — they need to roll back all the changes.
  2. To quickly roll back any new features, developers should use separate branches for different features.
  3. To avoid timing troubles, — never make deploys late in on Friday evenings.

Testing your software is a crucial part of the deployment cycle. By running through tests before, during, and after deployment, you can improve the quality of your software and ensure a better product.

Master of Code is an Agile software development firm that specializes in crafting world-class web and mobile software products. We’d love to hear your feedback and best practices when it come to how your team tests software. Plus, we are always here to help if there’s anything we can do to help.



Mastery Matters!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store