Quantum Mob's Principles of App Testing
We hope this helps you better understand the perspective of the engineers creating your app.
Table of contents:
We get it; Understanding code and development is hard enough. Now you, a client, are expected to test the latest work on your app and note any issues—otherwise referred to as bugs—without fully understanding what they are, why they’re there, and why your product is being shown to you ‘unfinished’.
From a Development Perspective
We need you to see the features we’ve developed and simply touch base on
those aspects that are important to you—especially those you feel you
need in order to keep moving forward.
While brief, we hope this helps you better understand the perspective of the engineers creating your app.
The features you end up testing should be as close to market-ready as possible. That’s why we work in constant open communication with you and your stakeholders, in order to develop a product that meets market needs with a competitive edge.
You need to test your app on different devices, screen sizes and OS versions. This lets you see how users will interact with your app, but also how the product reacts to the various platforms and technology that support it. Keep in mind, you shouldn’t be testing on an unusual browser or platform if it doesn’t apply to your target audience. (eg. an Xbox web browser)
Is the software 'stressful' to use? Are key performance aspects bothering you? If so, why? This is important because for applications in a competitive market, usability is key.
Developing an application is like building a house; you don’t need to worry about how the paint colours look if the walls haven’t even been built.
With this in mind, most of your efforts reviewing the app should focus on completed features. A feature in progress may have bugs that have been noted and possibly fixed since you had the chance to test. However, if a feature has been marked as complete and it falls short, it’s best to provide that feedback as soon as you can. Completed features should be clearly indicated in a project management tool like JIRA or Trello, or an email with a feature list. If this isn’t the case, reach out to your representative.
Your feedback is a key component within the agile process and is crucial to our processes. If the feature set that has been delivered is being iterated on or is particularly complex;
tightening the feedback loop will allow for necessary pivots in a timely manner, leading to greater satisfaction for everyone involved.
You know what’s best for your product, and you have a vision that we want
to bring to life. Plainly stated, that’s why we need you to test your apps.
Do you have any questions about testing a web or mobile app? Send us a question at [email protected].
Receive summaries directly in your inbox.