Heading

Heading

Heading

Heading

button text
Text Link

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.

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

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. Talking, emailing, documenting.
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 breakthe code between the new feature and the existing functionality).
step
06
Testing (white and black box manual testing, automation testing;documenting the bugs).
step
07
Regression Testing (ensure ALL the different elements like the userauthorization and payment data corruption work together properly).
step
08
Release: have 1 front-end and 1 back-end engineer on deck for hotfixesduring and immediately after the release - before users notice.
step
09
Smoke and Acceptance Testing (make sure corefunctionalities work seamlessly).
step
10
Delivering the results to the product manager (usually, depending on the 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.