QA Cheatsheet

1. Acceptance testing

Start simple: test whether the feature works as expected. This is the core of your QA cheatsheet—ensuring that the feature meets the basic acceptance criteria.

2. Functional aspects

Check each element of the app and compare it against the written functional specification. This is known as validation. A QA cheatsheet should remind you to carefully review each functional aspect.

3. Fields – test for these conditions

Make sure to thoroughly test fields for the following:

• Initial button state

• Conditions for field availability (ON or OFF)

• Min/Max input limits

• Accepted characters

• Field requirements

• Backend vs. frontend validation

• Does an empty space count as input?

• Behavior with invalid characters

• Copy-paste functionality

• Microphone input

4. Button testing

Verify the behavior of buttons under different conditions. Test how the app reacts when invalid data is entered and the button is pressed. This part of your QA cheatsheet will help you ensure that error handling is on point.

5. Keyboard testing

Check the initial keyboard state and ensure that the return or “done” button works as expected. Test non-standard characters from the UTF-8 catalog, and ensure that the predictive text feature works (except in password fields). This step should always be included in your QA cheatsheet to avoid overlooking keyboard behaviors.

6. Test data behavior

Test how the app behaves with duplicate data, removal of data, expired data, and check for spelling mistakes. These small details can often be overlooked, but a good QA cheatsheet will remind you to focus on them.

7. Navigation testing

Test navigation back and forth. Check if the data entered into the fields is saved while navigating or if it gets lost. Make sure any links within the feature lead to relevant destinations.

8. Device integration

Test how the feature behaves with external factors, like receiving a call or text message. Test Wi-Fi disconnections, changes in screen orientation, and uninstalling/reinstalling the app. This is especially important in your QA cheatsheet to account for every possible external disruption.

9. Cross-platform testing

Test the feature on both iOS and Android. Make sure the feature performs well across common screen sizes and lower-performing devices. Your QA cheatsheet should also guide you to test under stress conditions, like when other apps are running and throttling the device’s memory and CPU.

10. User-friendliness

Ensure the feature is intuitive and user-friendly. It should also respect platform guidelines, as UI approaches may differ between iOS and Android. This is a key item to check off in your QA cheatsheet to make sure the feature aligns with standard user experience practices.

11. Compatibility testing

Check for backward and forward compatibility with different versions of the product. Ensure the feature works across various versions and platforms (e.g., iOS vs. Android).

12. Language and regional testing

Test the feature in all approved app languages and check regional settings. Ensure that accessibility options are also covered, as they can make or break the user experience for some users.

13. Security testing

Look for vulnerabilities and potential data leaks in the feature. Security should always be on your QA cheatsheet, as overlooking this can lead to major issues later on.

14. Sync testing

Check how local data syncs with the server, especially under different network conditions. Test the functionality across multiple devices with the same account to ensure everything stays in sync. This is one of those tests that shouldn’t be skipped in your QA cheatsheet.

15. Design testing

Make sure the implemented UI matches the design specifications provided by the design team. A good QA cheatsheet will remind you to ensure the visual experience is consistent with the design.

16. Component integration testing

Test how the feature integrates with other components, such as login or SLA features. Verify its behavior with both valid and invalid data.

17. Performance, load, and stress testing

This is where you push the feature to its limits. Use scripts to simulate stress and observe how the app behaves when it’s near, at, or exceeding its limits. Make sure your QA cheatsheet includes specific stress tests to test the feature’s performance under load