Skip to content →

How to find defects in software?

How many defects are you able to find in any software? That’s the question that should be on your mind when you get involved in crowdtesting cycles.

Let’s say you are a techie with sophisticated knowledge about computer science. Guess what? it won’t really be helpful when you freelance at crowdsourcing websites.

Your payout depends on the number of defects found. Period. So the logical assumption is that you gotta find a lot of defects, right? I’ve composed a list which may come in handy in your crowdtesting bugs hunting. Note that depending on the crowd platform criteria, some defects could be considered out of scope. Anyway, here are the scenarios that worth giving a try:

Web applications testing

Register/Login page

 Check the validation messages for all required fields

  • for some fields validation messages may be missing
  • messages could be incorrect – example “This field is required” instead of “The -e-mail format is incorrect”)
  • Try to register with an incorrectly formatted e-mail, use different variations “1@gmail,  @gmail.com –@test.com etc”

 Try to set a password, not meeting the complexity requirement

  • 1 character password
  • mismatching passwords in “Password” and “Confirm password” fields
  • set password containing space and try if you are able to login in afterward

 Check reset password functionality

  • try to input passwords not meeting the complexity requirement there
  • open the link with reset password in a different browser and try to log in from the other browser (often causes problems)

 Check “remember me” functionality and verify that your session persists after closing the browser window and conversely that the session is destroyed when this option remains unchecked

✔ After successful registration log out and click on the back button, if any personal info is shown, it’a defect (a very common one )

Product list

  • Verify if sorting works for each option (price, name, date)
  • ❗ Please don’t be lazy ❗ If the products are sorted by name in correct alphabetical order on the first page go and check other pages, the order may not be valid there
  • Check that filters are correctly applied
  • ❗ Once more don’t be superficial ❗ For example, when you apply filter size “10”, open the product details page of at least several products shown and make shown that each is available in size “10”
  • Meticulously browse products categories, you may encounter a shirt shown among “Hats” and a pair of sneakers that got lost in “Coats” sections.

Product details / Cart

  • Verify the validation if adding products without specifying color, size or another parameters
  • Check that clicking on “Add to cart” button increments the number of items for that product in the cart
  • Add the product to the cart as a guest user, register a new account and check if the product is available for a newly created user
  • As authenticated user add products to the cart and wish-list, log out and log in again, check if the items from the wish-list and cart are preserved
  • Add the maximum allowed quantity of the item to the cart, verify the limits handling
  • Decrease quantity and verify it’s correctly updated
  • Set quantity to 0 and verify that cart has been emptied
  • Add multiple products (preferably with discounts) and check if the prices are correctly calculated
  • Click on Back button and make sure that previously deleted items don’t show up in the cart
  • During checkout try different credit cards, including 15 and 19 digits card numbers (google “test card numbers” and use them for testing)

Mobile testing

Besides the relevant scenarios above add the following:

Native mobile apps

  • Disconnect the phone from Internet and check that message informing about offline status appears
  • Turn off the Internet when submitting any form, resume the connection (often in such cases infinite loading occurs – you won’t believe how many defects of this kind get logged in crowdtesting sites)
  • Switch the device language and verify that the app in question functions as intended
  • Check if data and settings are preserved after back-grounding and foregrounding the app
  • If the app involves interaction with the sound or video, interrupt the flow with a phone call and check if the sound stops playing
  • Verify that the back button is always working and redirecting to the previous screen

Mobile web

When testing web applications in mobile browsers, additionally:

Switch to landscape orientation (this way you may find lots of problems with UI, virtual keyboard overlapping the whole screen, some key functionality not accessible this way, etc.)

 Verify that it’s possible to use a virtual keyboard and that the buttons and actions are correct:

  • When navigation from one field to another – should be able to use Next button (in Android, often not the case)
  • Should be able to submit any form tapping on “Go” button

 Check hamburger menu, verify it allows to scroll (if possible), navigate to any item on the menu and doesn’t malfunction when switching portrait/landscape orientation

Ok, what have I forgotten? Let me know and I’ll include that to the list:)

 

Published in Crowdtesting

One Comment

  1. GreggDromi GreggDromi

    Хорошая статья

Leave a Reply

Your email address will not be published. Required fields are marked *