Qa Cheat Sheet

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 7

QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.

co/blog/qa-cheatsheet/

GUIDES & TUTORIALS

QA Cheatsheet
SEPTEMBER 4, 2019  0

INTRODUCTION

Our QA cheatsheet is a must-read before trying out a new feature.

Before we start, validate that the newly added feature integrates


well with the existing system.

Most times, developers don’t know the entire product as well as a


QA (who investigated it thoroughly). There will be a lot of edge
case bugs if you do some boundary testing.

QA CHEATSHEET FOR TESTING A NEW FEATURE:

1. Acceptance testing – simply test if the feature works or not.

2. Functional aspects. Take each element of the app and compare


it to the written functional speciTcation – this is called validation.

3. Fields – have to be tested for:

• initial button state;

1 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

• conditions for 9eld availability ON or OFF;


• min or max;
• accepted characters;
• requirements;
• backend validation vs. frontend validation;
• does an empty space count?
• behavior with characters that are not accepted;
• check how and if copy-paste works;
• microphone input.

4. Button testing:

• Verify conditions for Teld availability ON or


OFF, negative and positive testing, as well as error handling

• Fill out invalid data in one or more Telds and press a button to
see how the app reacts.

5. Keyboard testing:

• Look at the initial keyboard state; check for a return or a done


button, as expected.

• The predictive text function should work properly, except for


the credentials Telds.

• Input non-standard characters by picking some from the UTF-8


catalog. Also, try to see how the app behaves
with funky characters.

6. Testing duplicate
data behavior, removal of data behavior, expired data behavior,
and spelling mistakes (must be thoroughly checked).

7. Navigation testing – back-and-forth navigation.

• Check if the data you populated the Telds with remains saved

2 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

while browsing or if you have to repopulate it.

• If there are links within the feature, check to see if they are
relevant.

8. Device integration – how the feature behaves with external


factors.

• Check how the feature acts when you receive a call or


a text message, Wi-Fi is suddenly disconnected, or the user
is disconnected via 3rd party.

• Change the screen orientation and check the feature.

• Uninstall the application, reinstall it, and check its behavior.


Also, try installing it with an older build existing side by side.

9. Cross-platform testing – test the feature on the accepted iOS


and Android versions.

• Test the most common screen sizes. They can distort the UI in
an erroneous way.

• Test the feature on devices with low performance.

• Devise some stress tests and see how the app behaves when
you load up a bunch of other apps and throttle down the
available device memory and CPU power.

10. Test the feature to be as user-friendly as possible.

• The feature must also respect the OS standard approach as it


might differ between iOS and Android.

11. Compatibility testing – check


for backward or forward compatibility with other product
versions.

3 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

• See how compatible it is with other platforms (e.g., iOS vs.


Android).

12. Test if the feature is working and showing up properly in all


approved app languages.

• Test any other regional settings – check if the application


respects them.

• Accessibility options should also be tested – see how the app


behaves.

13. Security testing. Check for vulnerabilities within the


application and information possibly being leaked to other
destinations.

14. Sync testing – check when the local data gets synced to the
server.

• Use a network throttle tool to check the functionality on


different bandwidths. Check how the feature communicates
with the cloud when testing the sync function.

• Try to perform test syncs while dropping the Wi-Fi before, in


the middle, and after the connection is processed to the cloud.

• Using the same account, try to perform changes


using multiple devices.

15. Design testing – Is the implemented UI the same as the one


sent by the designers?

16. Component integration testing – check out how the feature


integrates with existing sibling features, e.g., how Login or SLA
affects the feature.

• Check using valid and invalid data.

4 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

17. Performance testing, load testing, and levels


of stress testing.

• Use scripts to reach the speciTcation limit and closely monitor


the app when it’s close to the limit, at the limit, and above the
existing limits.

WEB-RELATED TESTING AND API TESTING:

*Not limited to the web.

• Multiple browsers compatibility.

• Windows resizing – the UI elements should still appear


properly, regardless of the differences between screen sizes.

• Try logging in on the same account on multiple tabs and


doing contradictory edits to the same data object (e.g., patient
data).

• Check if the selected data in the UI is the one that


is actually sent to the server once the Send button is clicked.

• Make sure the request isn’t sent more than once if you tap a
button multiple times.

• Validate 9eld limits and see if the same limit exists on both the
server and client sides.

• Check the error status handling on the client


by faking bad data and modifying the requests received from
the server-side (using Charles, for example).

• Block API requests using Chrome – see how the client handles
a blocked request.

5 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

• Edit API request payload using Charles – see how the client or
server behaves with unexpected data.

We hope this list is useful to anyone trying to make sure nothing


important was skipped while performing quality assessments.

Stay Updated with the Latest in QA

The world of software testing and quality assurance is ever-


evolving. To stay abreast of the latest methodologies, tools, and
best practices, bookmark our blog. We’re committed to providing
in-depth insights, expert opinions, and trend analysis that can help
you reTne your software quality processes.

Visit our Blog

Delve deeper into a range of specialized services we offer, tailored


to meet the diverse needs of modern businesses. As well, hear
what our clients have to say about us on Clutch!

 SEE THE OTHER SERVICES WE PROVIDE

betterQA code developer independentteam QA Cheatsheet qatesters

qatesting Software Testing softwareengineers testers testing thirdparty

SHARE THIS POST    

6 of 7 9/22/23, 12:01 PM
QA Cheatsheet To Quickly Help With Your Testing Needs https://betterqa.co/blog/qa-cheatsheet/

EXCELLENT

38 REVIEWS

Get in Touch

Address: 28-30 Anton Pann street, Cluj-Napoca 400053, Romania


Phone number: +40 751 289 399

GDPR

PRIVACY POLICY

7 of 7 9/22/23, 12:01 PM

You might also like