A basic quality assurance (QA) process

In order to have a good QA process you have to make sure the correct inputs are in place before starting on an piece of work.

  • An Epic must have a brief, a concept (or research). A design (or diagram)
  • A Story must have a specification with acceptance criteria
  • A Bug report must have steps to reproduce, current behaviour, expected behaviour, and browser

Once we have the right inputs and work has been completed by a developer the the following process should be followed.

  1. Code is pushed to a branch on the development server
  2. Developer re-reads the specification, tests the functionality against the acceptance criteria and signs off as complete
  3. Deployment notes should be written
  4. A code review should be performed and signed off
  5. Code is pushed to the UAT server
  6. Test on one mobile device and one desktop device
  7. Testing on the other browsers/devices (types depend on the level you’d like to go to and the analytics on your user base)
  8. Once all code for a sprint is on the UAT server then a full site test should be performed to uncover any regression bugs
  9. Code is pushed to a the live server
  10. A full live site test should be performed, especially the booking path

This will ensure that you have an almost bug free product.