Initial meeting to discuss what testing is required for your application or website testing project. Depending and the size and scope of the project this can be done via email, Phone call or skype.
The aim of this first stage is to not only get an idea of the size and scope of the project and what testing is required but also determine if we are a right fit.
During this phase, we can also discuss the best way of reporting issues to your developers.
During this phase, the website or application is tested, based on the parameters set during our initial meeting. This will include a range of testing types agreed on, plus will also include open ad-hoc testing to find bugs that may be hiding in the application/website.
Issues found during this phase are reported using the agreed upon method, This could range from your own issue tracking software such as Jira, Test Track Pro, Or even within a google doc or excel sheet. Whichever works best for your development team.
Results of testing will be reported in a range of different ways depending on the scope of the project and what is agreed upon with the client. For small short term projects this could be reported via email summarizing the results of the test. For longer, larger scope projects results can be reported in a full test summary report.
During this final stage, we discuss if any further testing is required.
This could include further focused testing of specific features, regression testing to ensure that previously fixed bugs have been resolved or further exploratory testing to ensure no hidden bugs remain un-found