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.
- Code is pushed to a branch on the development server
- Developer re-reads the specification, tests the functionality against the acceptance criteria and signs off as complete
- Deployment notes should be written
- A code review should be performed and signed off
- Code is pushed to the UAT server
- Test on one mobile device and one desktop device
- Testing on the other browsers/devices (types depend on the level you’d like to go to and the analytics on your user base)
- Once all code for a sprint is on the UAT server then a full site test should be performed to uncover any regression bugs
- Code is pushed to a the live server
- A full live site test should be performed, especially the booking path
This will ensure that you have an almost bug free product.