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

  • Unhappy users and bad reviews?

    Get the bug reports you want done by Rockstar QAs, ASAP.

  • No budget or equity for a QA?

    Enjoy a hassle-free way to get your testing done, guaranteed.

  • Want professional communication?

    We work across 7 timezones and communicate clearly, promise ;)

ILoveMyQA’s 10 Steps to Effective Testing will reduce cost

Make sure the QA team, the front/back-end engineers, and the product manager have coffee on hand to deal with anything unexpected that arises ;)

  • Step 01

    Verify SOW with all relevant parties. You’d be surprised how much time this saves!

  • Step 02

    Collecting requirements from the customers, product owners, designers, developers even before the feature was implemented.

  • Step 03

    Writing a test plan, test cases, check lists.

  • Step 04

    Setting up the environment correctly.

  • Step 05

    Compatibility testing (make sure our dev team didn’t already break the code between the new feature and existing functionality).

  • Step 06

    Testing (white and black box manual testing, automation testing; documenting the bugs).

  • Step 07

    Regression Testing (ensure ALL elements like user authorization and payment work together properly).

  • Step 08

    Release: have 1 front-end and 1 back-end engineer on deck for hotfixes immediately after release.

  • Step 09

    Smoke and Acceptance Testing (make sure core functionalities work seamlessly).

  • Step 10

    Delivering the results to the product manager (usually, depending on internal workflow).

Bug Template

Yup, it's written in English you'll understand, with bullet points, well-composed and easily breaks down how to reproduce issues.

A table with case name, steps, expected result, actual result, environment, references headings

← Scroll horizontally to see full report →