FAQ | Testing Forward

What if our tech stack isn't mobile or React?

My expertise is specifically in iOS, Android, and React/frontend testing. If your highest-pain bugs are in backend services (Python, Java, etc.), I'm probably not the best fit for this engagement. However, if you have a mobile app or web frontend with testing gaps, that's exactly where I can help. During our initial conversation, we'll confirm whether there's a good match.

How do you define "2-3 bugs" worth of tests in Week 2?

I'll write targeted unit tests that recreate the exact failure scenarios from your most costly recent regressions. For example, if you had a bug where discount codes applied twice, I'll write tests proving that scenario is now caught. The goal isn't volume—it's demonstrating how automated tests prevent real bugs you've actually experienced.

What if we don't have 6 months of bug history documented?

No problem. I'll provide a simple spreadsheet template for your team to fill out with regression bugs they remember from the past 3-6 months. Even if they only recall 5-10 bugs, that's enough to identify patterns and demonstrate value. We'll work with whatever level of documentation you have—formal bug tickets, Slack conversations, or team memories of "that time when X broke."

Can you work with our existing test framework?

Yes. I'll use whatever testing framework you're already using (XCTest, SwiftTesting for iOS, JUnit/Espresso for Android, Jest/React Testing Library for web). If you don't have one yet, I'll recommend industry-standard options and explain the trade-offs.

What happens after the 3 weeks?

You'll have everything you need to continue expanding coverage on your own using the playbook and roadmap I provide. Some clients engage me for follow-on work (additional features, training sessions, ongoing advisory), but there's no obligation. The pilot is designed to give you immediate value and long-term independence.

Do we need to dedicate engineering time to this?

Minimal. I'll need 1-2 hours from your Product Owner for the initial interview and maybe 30 minutes from an engineer for codebase access/setup. The final presentation in Week 3 is optional but recommended (30-45 minutes with leadership). Otherwise, I work independently.

What if our codebase is too messy or legacy for testing?

I've worked with codebases of all ages and conditions. Even legacy code has testable entry points. I'll identify practical starting points that don't require massive refactoring. If something truly can't be tested without major changes, I'll document that in the roadmap with effort estimates.

How is this different from hiring a QA consultant?

Traditional QA consultants often focus on manual testing processes or test automation at the UI level. I focus specifically on unit and integration tests at the code level—the kind that run in seconds and catch bugs before they reach QA. I'm also coming at this from an engineering leadership perspective, not just testing in isolation.

What about the AI stuff you mentioned?

I'm researching how AI could eventually automate the analysis I do manually—mapping user scenarios to test coverage at scale. But that's separate from this engagement. You're getting proven hands-on consulting now. If I develop tools based on this research, you'd have early access as a founding partner. Your value is guaranteed regardless of whether that materializes.

Can we get a refund if we're not satisfied?

I'm confident in the value I deliver, but yes—if after Week 1's analysis you don't see value in continuing, I'll refund 50% of the fee. My goal is to prove ROI early so you're excited to continue.

Frequently Asked Questions