LAB NOTES

10 QA Tips for Mobile App Development

Worry Free Labs10 QA Tips for Mobile App Development
10 QA Tips for Mobile App Development
Worry Free Labs10 QA Tips for Mobile App Development
Quality Assurance "QA" can often be overlooked or not receive the proper amount of attention compared to other aspects of mobile app development. We at Worry Free Labs believe having a strong QA process will help with mobile app development and can save an enterprise time and money in the long run.
1. A QA team is instrumental to developing and launching a successful product. The QA team is responsible for ensuring that the development team stays within the guides of a planned process; all requirements identified as part of the product release are addressed and met; and the software is defect-free, or is released with an accepted list of known issues.
2. QA should be built in to all aspects of the product launch. QA is instrumental in process improvement as well as defect management, security testing, accessibility testing, performance testing, and user acceptance testing. In an agile environment, the mantra is “test early and test often”. As such, QA should be included in the product plan as a critical part of the team.
3. QA should be involved in the product launch process from the very beginning of the project. The QA team is responsible for creating the test plans, test cases, and automated test scripts. Again, test early and test often.
4. Product teams should make QA an integral part of the team in order to make QA easier/better/faster. QA team members should be reviewing User Stories with the Product Managers as they are created to ensure they meet the “testable” criteria. They should be creating test cases prior to the start of the sprint to help facilitate test-driven design. They should be working side-by-side with the developers to test the new features developed each sprint, and should manage the deployment to the QA environment.
5. QA has many benefits for product development: Quicker sign-off – the product meets the client’s requirements; A quality mindset fostered by strong QA nurtures ongoing improvement; The QA team will improve stakeholder confidence in your ability to launch a successful product; and QA reduces the overall software life cycle cost – less maintenance.
6. QA tends to face hurdles due to schedule or budgetary reasons. QA is often the first to be cut or underestimated, since it is often viewed as simply a test of the software. Management also often wants to put the developers in charge of their own testing. Not a good idea. Ask any developer, and they will tell you that their code works! Finally, the main hurdle QA faces on a software development team is the “us vs. them” mentality. QA is not the enemy, it is key to delivering a quality product.
7. Startups vs. enterprise typically implement QA differently. An early stage startup typically struggles with getting as much done as quickly as possible with minimal funds. In this environment, QA is often overlooked or deferred in order to meet tight budget constraints, resulting in a less stable product. At the enterprise level, there is a tendency to let projects stagnate because of too much process. When this is the case, QA needs to revisit their processes to keep them streamlined, relevant, and nimble.
8. QA is an ongoing integral process for mobile app development. QA is integral to the full software development life cycle. It is not a test that is bolted on to the end of a development process. The longer you wait to fix a problem, the more expensive it is to correct.
9. QA needs proper resource allocation. We typically like to have one QA resource for every 3-4 developers. If the project calls for automated regression testing, then additional resources would be needed for automation. When QA is integrated into the full mobile app development cycle, testing should be complete at the end of each sprint and the product should be stable as you approach product launch. We recommend a 3-4 week hardening period prior to product launch to provide sufficient bandwidth to address production issues.
10. QA can lower the overall project costs. What is to cost of not having a solid QA program? A solid QA program should result in lower maintenance costs over the entire product life cycle. There are many options for QA resources that keep it affordable.
Are you in the midst of launching a new mobile app? Or maybe just getting to the strategy and planning phase? Either way, it’s never too late or too early to apply sound QA principles to ensure that you deliver the best mobile app possible in a timely manner. If you’re looking for a mobile app partner to help guide you through the process, contact us.
Drop us a note
we're just an email away!
470-223-4370