Assuring quality of mobile app. stage 4: release and supporting testing activities
We continue our mobile app testing series of articles. This time let’s discuss how testing team shall support the product at the release stage.
Once the first round of testing is over, it’s important to realize that it’s hardly ever enough to ensure outstanding quality of the product. The first round is usually followed by at least two more where bugs fixing and application stabilization should be verified.
Testers’ activities after the first round of testing
- Defects validation. After the defect was marked as Resolved in the bug tracking system, the reporter should check whether it can be reproduced again or not. If not – the bug is closed. If the problem still exists – reopened.
- New feature testing. If a new feature was added to the application, testing team should check it on all devices and compare the app performance with the previous build.
- Regression testing is a type of testing performed to verify the previously developed software still functions correctly despite the implemented changes (software enhancements, configuration changes, software deployment in new environment, etc.)
In most cases the app will gain high quality after several test iterations and can be shipped to the market.
The app should meet the following criteria to be fully ready for release:
- Lack of critical and major defects that will affect user experience.
- App compliance with online stores requirements. Non-compliance may result in the publication deny even if the app is 100% perfect.
Depending on the mobile platform you build your app on, the release checklist may contain the following issues:
- APK Extension files should comply with the requirements in the Dev Guide.
- The application interface should be developed according to the User Interface Guidelines.
- The application should possess a unique title and fall into one of the categories in the store.
- The application shouldn’t contradict the Human Interface Guidelines.
- The application can be published unless it contains banned materials or it duplicated the functionality of the already existing product.
Taking into account these and many other aspects you’ll ensure that the app is ready to be shipped.
That’s it. Now let’s briefly sum up the main peculiarities of the mobile apps testing:
- Strategy and selecting devices make a much bigger difference than for web and desktop systems testing.
- It’s a “must” to include specific mobile checks into test documentation.
- Utility programs can significantly facilitate your testing process (gathering stats, taking screenshots, etc.).
Make everyone feel the part of success
And the last tip that some managers neglect: thank your team once the project is over. It’s very important to know that you are valued. At the end of the day, the app’s release is the success of the whole team.
We are done! Thanks for taking your time to read the entire cycle of articles. We tried hard to compress the information we wanted to share in readable publications.
In the last post we’ll show you how we applied all this knowledge to ensure quality of one of the best-loved and best-known apps of 2016.
Sure you’ll enjoy the read.