Change analysis
First, we work with you to understand what we need to test. This includes any new designs and functionality changes. Then, we list out all the scenarios, browsers and devices that will need reviewing and testing.
Estimation
We’ll provide an estimated number of hours based on what needs to be tested, so you’re in the loop on timelines.
QA
Our QA engineers then go through all the changes that are live on the required devices and browsers. We can also use tools such as BrowserStack or CrossBrowserTesting, to ensure we don’t miss anything at all.
Bug reports
For each bug, our team will report the details of it, with screenshots or videos of the issues for reference. They’ll also confirm the device and/or browsers where the issues are happening and will note any additional observations. These are things that might not be potential bugs, but that we think are important to point out for you.
Check bug fixes
Once the bugs are reported as resolved, the team will rerun their testing, to ensure that the bugs are definitely fixed and that no new bugs have been created. This is when we confirm to you that the application is ready to go live for your customers.
Recording sessions
To have extra peace of mind, our QA engineers will record their screens, so you’ve got a record of the product being tested across different browsers and devices.
