Question 1

Do I need manual QA, automated QA, or both?

Accepted Answer

Most products benefit from both. Manual QA is essential for exploratory testing, usability validation, and edge cases that require human judgment. Automated QA is essential for regression testing, CI/CD pipeline validation, and catching regressions across a growing codebase. We typically start with manual QA and add automation once the product is stable enough for reliable test scripts.

Question 2

Can I hire QA without hiring developers from PettersonApps?

Accepted Answer

Yes. We offer standalone QA engagements where our testers embed into your existing team — whether your developers are in-house, freelance, or from another vendor. The QA engineer uses your tools, follows your processes, and reports bugs in your tracker. No dependency on PettersonApps development.

Question 3

How do you test across different devices and platforms?

Accepted Answer

We maintain a real device lab — not just emulators. For mobile, we test on the latest three iPhone generations, major Android devices (Samsung, Pixel, OnePlus), and iPads. For OTT, we test on physical Roku devices, Amazon Fire TV sticks, Android TV boxes, and Apple TV. We define a device matrix per project based on your user analytics and target audience.

Question 4

How quickly can a QA engineer start on our project?

Accepted Answer

Typically within 1–2 weeks. The first few days cover onboarding — understanding the product, setting up the environment, reviewing existing test documentation, and establishing the testing workflow. By the end of week one, the QA engineer is actively testing within your sprint cycle.

Question 5

What does the QA engineer deliver?

Accepted Answer

Each sprint: a test execution report with pass/fail results, bug reports with steps to reproduce and severity, and regression test results. Over time: a growing test case library, automated regression suites integrated into CI/CD, and a device coverage matrix. All documentation lives in your tools — Jira, Notion, Confluence, or whatever your team uses.

QA Testing

FAQ.

QA Testing

FAQ.