The Definitive 227 Item Quality Assurance Checklist to Test Before Launching New Software

You got an amazing idea… You nailed the UX… You got a beautiful UI… And you are all set to start developing your app. The fun, exciting and explorative phases are done and you are moving into execution mode. You want an incredible user experience to make your app the next big thing. What does it take? Testing, testing, testing…

Things to consider upfront (before you even start to develop)

Testing and Quality Assurance (QA) is a time consuming and sometimes dull task. But it’s critical to do in-depth testing in order to deliver an app your users will love 💖. Before you start developing your app consider the following:

• Which platforms does the application need to support? Web, mobile, tablet, desktop?
• Web: Which browsers need to be supported? Chrome, Firefox, Safari, Internet Explorer, Edge etc.?
• Mobile & Tablets: iPhone and/or Android? iPad and/or other tablets?
• Desktop: Windows app and/or Mac app?
• Compatibility: Are you only going to support the latest released OS and browser versions, or does it need to be compatible with older versions?

Assume you need to support 5 browsers + iPhone + Android, you need backwards compatibility on all platforms and to support different devices; then you’ll see how the testing effort quickly scales up.

Overall Test Approach

Follow these 5 tips to speed up testing and quickly find critical bugs:

1. Carry out cross-platform testing: Login with different users simultaneously on all supported platforms. Use both simulators and physical devices. You can now start testing.
2. Check the most important functionality, the overall flows etc. Variations, combinations, details and edge cases can be checked later.
3. Do everything that you think you shouldn’t be allowed to do!
4. Try to make the system crash!!
5. And of course check spelling, UI, design, alignment etc.

You can of course test a lot with simulators. But remember to test on physical devices as well. They sometimes provide slightly different results 😉

In-depth QA Tests

Here’s a detailed list of things to look out for in your current or next project. It’s a checklist for all members involved in your app development. Developers (backend + frontend), Designers (UX + UI), QA, QC, Project Managers, Product Owners and Support.

1. Sign up: Create account with email.
2. Sign up: Activate account via link in email.
3. Sign up: Create password. Which rules apply to the password? Small and capital letters, numbers and special characters, minimum length etc.
4. Login: Successful login.
5. Login: Auto-login when opening the app.
6. Login: Failed login using incorrect username and/or incorrect password.
7. Login: Lock account on too many incorrect login attempts.
8. Login: Reactivate account if it has been locked.
9. Login: Test social logins like Facebook, Google, LinkedIn etc.
10. Login: Test single-sign login.
11. Login: Test two factor authentication.
12. Log out: Log out from the application.
13. Log out: Log out of all devices.
14. Profile: Change password.
15. Forgot password: Verify that you receive a password reset email or SMS code and that the updated password works as expected.
16. Onboarding: Test all variations of the flow. E.g. if the onboarding splits up into different routes depending on a choice, if different templates/groups can be selected etc.
17. Onboarding: Check that you can’t proceed if the user needs to select a minimum number of topics to follow.
18. Onboarding: What happens if the user stops in the middle of the flow?
19. Onboarding: Test the email onboarding sequence after sign up. Maybe you use services like , or ?
20. Empty state: Does the application look properly (and good) when no content is shown? What happens when the first item is added?
21. Empty state: Delete all content and check the empty state.
22. General: Is each field in the application the correct type? Single line of text, multiple lines of text, numeric, yes/no, dropdown, choice, lookup, date, time, person, calculated value, link etc.
23. General: Can the field be edited or is it a view-only field (locked for editing)?
24. General: Does the field have a minimum or maximum length? Does it require an exact number of characters (like credit card details where you need to provide an exact number of characters)?
25. General: Highlight selected field.
26. General: Display hint text in fields. Hide after the first character is added. Show hint text again if all characters in the field are deleted.
27. General: Auto-capitalize text fields.
28. General: Test if the field is case sensitive.
29. General: Use special characters like &, ‘, %, æ, etc.
30. General: Try to add spaces in all fields.
31. General: Is it okay to have blank/empty fields? What if you insert a space and try to save?
32. General: Type-ahead, are suggestions provided?
33. General: Copy/paste text, hyperlinks and email addresses.
34. General: Try to add emojis (e.g. by copy/paste from ).
35. General: Try to type text in dropdown and time picker fields.
36. General: Can you select multiple items when you should only be able to select a single value and vice versa.
37. General: Set date in the past. Set date in the future e.g. next year.
38. General: Show help text underneath fields.
39. General: Show validation rules (e.g. when creating passwords).
40. General: Are items updated in realtime?
41. General: When should long text be truncated?
42. General: Verify dynamic calculations are correct like storage used, number of episodes available etc.
43. General: Test navigation. E.g. cancel, go back one step, tap outside of popup etc.
44. General: Check error messages.
45. General: Pick up where you left (remember last state). E.g. which page you last had open, which document you last viewed, how far into the podcast you had listened etc.
46. General: Check that online/offline status appears correctly. Try to be online on several devices and shut down one after the other until you are no longer connected.
47. General: Check if sharing works as expected.
48. General: Can follows/likes be unfollowed/unliked? Is it dynamically reflected for other users.
49. General: Check business rules if you have fields which are dependent on each other. E.g. if values filled in one field narrow the options available in the next field. Go back and change a previous field. Verify that dependent fields are updated/cleared.
50. General: Check business rules where a field is hidden until a specific value has been filled in in the previous step.
51. New: Create a new item.
52. New: Quickly add new items one after the other.
53. New: Copy/duplicate an existing item.
54. Update/edit: Update an item and save it.
55. Update/edit: Try to add incorrect input in a field (e.g. letters in a numeric field).
56. Update/edit: Verify data is correctly saved — and displayed when you open the item again.
57. Update/edit: Modify multiple fields (add content in some fields, delete in other fields, modify in some fields) and verify that data is saved correctly.
58. Update/edit: Drag and drop to update items.
59. Update/edit: Change icons.
60. Update/edit: Check simultaneous editing with two users logged in and editing the same item at the same time.
61. Update/edit: Can you archive an item?
62. Update/edit: Bulk update items (e.g. if the name of your organization changes and you need to change all metadata in the system).
63. Update/edit: If you have a locked item (e.g. an approved document), are some metadata “less important” allowing you to edit them? Example: Assume again that the documents have been tagged with your organization’s name and you want to update this.
64. Delete: Delete an item (or leave a group).
65. Delete: Verify deleted items are removed in real-time.
66. Delete: Recover deleted items.
67. Delete: Permanently delete items.
68. Multiple items: Upload multiple items/files/images. Show spinner, progress bar or upload in background to indicate progress to the user.
69. Multiple items: Select multiple items.
70. Multiple items: Move multiple items.
71. Multiple items: Delete multiple items.
72. Popups (modals): Add text in required fields → Create/save button becomes active.
73. Popups (modals): Delete text in a required field → Create/save button becomes inactive.
74. Popups (modals): When clicking outside the popup, should the popup be closed, content saved or should it be kept open?
75. Text & Messages: Try to save/send if no text is entered.
76. Text & Messages: Send a single line of text.
77. Text & Messages: Send long messages (e.g. +256 characters).
78. Text & Messages: Use SHIFT+Enter for line breaks.
79. Text & Messages: Send emojis.
80. Text & Messages: Expand field if the user adds multiple lines? How much should the field be able to expand?
81. Text & Messages: Add cursor in the beginning, middle and end of existing text. Then add some new text. The existing text must remain.
82. Text & Messages: Add cursor in the beginning, middle and end of existing text. Then paste some text. The existing text must remain.
83. Text & Messages: Add emoji in the middle of text — existing text must remain.
84. Text & Messages: Indicate when other users are typing.
85. Text & Messages: Indicate if a message is read.
86. Text & Messages: Correct rendering of emojis across platforms.
87. Text & Messages: Unicode conversion for emojis.
88. Images: Add image.
89. Images**:** Preview images including different resolutions and image ratios.
90. Images: Zoom in/out.
91. Images: Swipe quickly between images.
92. Images: Draw, manipulate, rotate and save changes.
93. Images: Delete image.
94. Files: Upload all types of files (doc, docx, xls, xlsx, jpg, png, pdf, mp4, zip etc.).
95. Files: Upload small and large files.
96. Files: Upload files with different URL encoding.
97. Files: Open and preview all file types (or a defined subset) and with different URL encodings.
98. Files: Download all file types.
99. Files: Rename files. Test file names which include special characters like ‘.
100. Files: Upload as new version.
101. Files: Upload and replace existing document — or avoid current documents with the same name to be overwritten.
102. Files: Add folders and subfolders.
103. Files: Navigate (expand/collapse) folders and subfolders.
104. Files: Re-arrange folders and nested folders.
105. Files: Check document versioning (minor and major versions).
106. Files: Create PDF versions from other file types.
107. Files: Print files or lock generated PDF copies for printing.
108. Links: Received links are clickable.
109. Links: Check all links work as expected.
110. Video: Record and add video.
111. Video: Play/preview video.
112. Calls: Check features like voice, video, screen sharing and take over control.
113. Calls: Check for issues where the microphone cannot be unmuted. We’ve experienced this often in the past when using e.g. Skype for Business where clients could hear us but we couldn’t hear them. Forcing the guests to leave and reconnect; and ultimately call by phone.
114. Forms: Test the processes from the first to the last step.
115. Forms: Test all loopbacks in the flow.
116. Forms: Should previous steps be locked for editing? When to reopen for editing?
117. Workflows: Test the primary flow where you only select positive outcomes.
118. Workflows: Test all major flows with all loopbacks.
119. Workflows: Start a workflow while another workflow is running.
120. Workflows: Terminate workflow.
121. Electronic signatures: Does it require username and password?
122. Electronic signatures: What happens on rejection?
123. Electronic signatures: What happens on approval?
124. Audit trail: View audit trails.
125. Audit trail: Verify dates, events, usernames/ID, old value, new value etc. are correctly captured in the audit trail.
126. Audit trail: Try to modify audit trails.
127. Audit trail: Try to delete audit trails.
128. Audit trail: Export audit trails.
129. Security: Check the permission model.
130. Security: Try to access content you are not allowed to.
131. Security: Check if you can see fields which should be hidden for you
132. Security: Try to edit content you are not allowed to edit.
133. Security: Try to start workflows you are not allowed to.
134. Security: Verify only available workflows are present.
135. Security: Who can participate in workflows?
136. Security: Who can sign off?
137. Security: What’s allowed to do on minor/major versions of a document?
138. Security: Try to inject malicious code into the fields in your application.
139. Security: Check that only admin account/users have access to the admin console and that ordinary users can’t access it.
140. Security: Verify that different organizations can’t accidentally see/access each others data.
141. Performance: Check latency from different countries (globally).
142. Performance: Check what happens if the connection is interrupted.
143. Performance: Should data be cached?
144. Performance: Do you used local dbs? Check data is stored correctly, what happens if an item is deleted etc?
145. Performance: Load old content dynamically, in background, upon scroll etc.?
146. Performance: Test number of users logged in at the same time.
147. Performance: Carry out load testing.
148. Backup: Test of backup (full backup + incremental backups).
149. Backup: Test of restore from backup.
150. Offline mode: Should content be accessible offline?
151. Offline mode: Sync when wifi/carrier signal is back.
152. Offline mode: Check for sync/merge issues when multiple users try to modify the same item in online/offline mode.
153. Invitations: Validate email address on Enter.
154. Invitations: Validate email address on “Send/Add” without pressing Enter.
155. Invitations: Invite multiple people. Try to use a long string, without separators, with space, with a comma, with semicolon etc.
156. Invitations: Incorrect email addresses (without @, with spelling mistakes like @gamil.com instead of gmail.com etc).
157. Invitations: Verify that invitation emails are sent and received.
158. Invitations: Can you access contact details from your email, device or the friends’ list in the application?
159. Referral program: Does the referral program work? Do users e.g. get the expected credit when the people they invited signs up (ala Dropbox and Uber)?
160. Premium: Does the payment module work?
161. Premium: Do users have access to premium features after they upgrade?
162. Premium: Downgrade account and check that access to Premium features are removed (immediately or on the expiration of the subscription period).
163. Reorder: Reorder items and verify that the ordering is kept and displayed correctly through all platforms.
164. Reorder: Have a list with more than 10 items. Reorder items in the range 1–10 and +10 and check that the ordering is saved correctly.
165. Favorite: Mark/star/favorite/pin an item. Verify that the item is not affected when reordering items or applying sorting.
166. Sorting: Check sorting (Alphabetic, Deadline, Categories, Create date, Tags etc.).
167. Sorting: Check sorting is not case sensitive.
168. Sorting: Check date sorting using different years, months and days.
169. Sorting: Check numeric sorting. The classic 1, 10, 11, 12… 2, 21, 22.
170. Sorting: Have the app open with two different users using different sortings. Let one user edit an item. Verify that the correct item is updated on the second user’s screen.
171. Filters: Check filters work as expected. Can multiple filters be applied simultaneously?
172. Filters: Assume you want to filter on a specific user with the initials “NJ” and there’s another user with the initials “NJI”. Does the filter only show items which exactly matches “NJ”? Or does it also include results for “NJI”?
173. Search: Are suggestions provided when you start typing?
174. Search: Are the expected results returned?
175. Search: Do you only see content/results which you are allowed to see?
176. Views: Check different views and that data is displayed correctly. E.g. list view, tile view, thumbnail view, tabular view etc.
177. Views: Toggle items on/off (like in calendars) and verify that the correct data is displayed in the view.
178. Views: Expand/collapse views, hide/show columns etc.
179. Reports & Dashboards: Verify that data displayed in dashboards are correct.
180. Reports & Dashboards: Verify that data are correctly pulled into reports.
181. Settings: Change team settings. Verify it applies for all users in the group.
182. Settings: Change individual settings. Verify that it doesn’t affect any other user in the group.
183. Settings: Change the time zone and verify that timestamps are correctly reflected for all users.
184. Settings: Should the language in your app be shown according to the default detected language in the browser? Can it be manually changed?
185. Notifications: Check if relevant notifications appear in your notification center.
186. Notifications: Can you clear notifications?
187. Notifications: Are notification cleared after an item has been viewed?
188. Notifications: Turn-off email notifications and verify that they are not sent.
189. Notifications: Check that unsubscribe to emails work as expected.
190. Notifications: Verify that alarms/reminders go on off on the scheduled time.
191. Notifications: Are people notified when mentioning them? What happens if they have disabled notifications?
192. Notifications: When the user follows a link in an email notification where should it open? Should it re-direct to the mobile app or web app?
193. Shortcuts: Copy/paste.
194. Shortcuts: Use of TAB between field.
195. Shortcuts: Use of other keyboard shortcuts.
196. Tools: Check import tools.
197. Tools: Check export tools including printing.
198. Tools: Check migration tools (export then import).
199. Browsers: Check functionality in Chrome, Firefox, Safari, Internet Explorer, Edge etc.
200. Browsers: Check compatibility with previous browser versions.
201. Browsers: Check scroll (vertical + horizontal).
202. Browsers: Check that content is still shown correctly if you resize the browser. Check the browser size with e.g. to see how it looks on e.g. a MacBook with a resolution of 1366 x 768 pixels.
203. Browsers: If you use a hellobar (e.g from ) check that it doesn’t impact the UI of your application.
204. Mobile: Update content in the navigation bar dependent on which screen the user has selected.
205. Mobile: Keyboard appears when a field is tapped.
206. Mobile: Keyboard is dismissed on scroll or tapping elsewhere on the screen.
207. Mobile: Check swipe gestures.
208. Mobile: Tap quickly anywhere on the screen (also outside of fields, near the border of the screen etc.).
209. Push notifications: Do you receive push notifications in killed state?
210. Push notifications: Do you receive push notifications when app is running in background?
211. Push notifications: Do you receive push notifications when app is in foreground?
212. Push notifications: Do you receive push notifications when the app returns from offline mode to online mode?
213. Push notifications: Turn-off push notifications and verify that you don’t receive push notifications. Turn it back on and verify that push notifications are received.
214. iPhone: Test backwards compatibility with iOS12, iOS11, iOS10… E.g. iPhone5 only supports iOS9.
215. iPhone: Clear badge count. When?
216. iPhone: Display push notifications in the notification center and when to clear them?
217. Android: Backwards compatibility (Oreo, Nougat, Marshmallow etc.).
218. Android: Are push notifications grouped correctly (if you group push notifications)?
219. Desktop app: Check functionality in Window desktop app.
220. Desktop app: Check functionality in Mac app.
221. Integrations: Can external apps be added inside your application?
222. Integrations: Do integrations to other apps work as expected? Are data exported, imported and sync’ed correctly?
223. Integrations: Have you tested your API?
224. Bots: Do your bots provide relevant information and correct answers?
225. Upgrades: Upgrade your data model. Check if anything breaks for users on a previous version. If things break, check that mechanisms to auto-upgrade them to the latest stable version works as expected.
226. Upgrades: If you deliver an on-premise solution (like SharePoint), test different upgrade paths from one version to another (direct from an exact version to the latest version, skip minor intermediate versions etc.).
227. Delete account: Ultimately, check that you can delete your account.

Speed vs. Quality

If you ship often and your app is feature-rich you’ll probably need one or more full-time QA engineers to ensure that you continouosly deliver a high quality app.

Move fast and break things. This was Facebook’s original motto. It may be a fine approach for early startups without too much traction but you (and your customers) need stability as you mature.

This is why Facebook changed their motto to Move fast with stable infrastructure since fixing bugs was slowing down development.

Facebook’s original and new motto.

How to help your engineers?

There’s nothing more frustrating for your developers if you say “it doesn’t work” without providing any details. Provide the following information to make your developers happy. It will of course also speed up the time to fix the observed issue 😉

1. Record the time the issue happened.
2. Make sure you can reproduce the issue consistently.
3. Describe the exact steps you follow.
4. Open your browser and press F12. Then reproduce the issue. Open the Console and Network tabs and provide the results to the developers. N.B. Clearing the data in the Console and Network before you reproduce the issue is a good idea.

Manual or Automated Testing?

If you build a cross-platform solution you’ll have a huge amount of test combinations. So you need to develop your test strategy wisely. Do the right amount of tests — not too little — but also do not test all combinations. If you are in QA but doesn’t have any coding experience, it might be worth talking to the engineers since some of the things you think is important to test might be irrelevant. You can setup automated test tools — or carry out manual test. What’s the best choice depends on the maturity of the product and the size of your company. Automated test tools sounds great, but you need a really mature product before it makes sense. You need to know that core features, UI and UX is not going to change for a long period. Otherwise, you’d constantly have to update the test script. Automated test tools also doesn’t spot things which are not right. It can be softer things like UI, spelling, alignment etc. which is important for the user experience.

Final Words

We built (a collaboration app for teams) based on lots of the principles and tests listed in this article. We’re curious to hear you best tips. Please comment below and we’ll update this post (to the benefit of all app developers, product managers, test engineers etc).

If you enjoyed reading this article or found it helpful, please clap 👏 and share it with your network. It would mean the world to us. Thanks.

has worked with IT project management and quality testing for +10 years and has originally a background from working with SharePoint. He is Founder & CEO of ; A team collaboration app designed to make teams move faster and collaborate efficiently. Without switching apps (or tabs) you can access your team’s tasks, files and messages.

SquidHub explained in 1 min 39 sec.

Thank you for reading — and have a productive workday!