Custom test execution: pick and run test cases across different features
Cherry-pick test cases with QA flow
Every QA team knows the drill: you need to run a quick smoke test before deployment, but your test cases are scattered across different features, different modules, sometimes even different apps. So what do you do?
The traditional approach? Create a dedicated smoke test suite. Copy or tag the relevant tests. Maintain documentation about what’s included and why. Update it when things change. Rinse and repeat for different scenarios.
There’s a better way
What if you could simply pick the exact tests you need, right when you need them?
That’s the power of cherry-picking with QA flow. Instead of managing rigid test suites, you can:
Select individual test cases from across multiple apps and features
Run them together as a one-time execution
Get instant results mapped back to each original app
Why this matters for smoke tests
Smoke tests are all about flexibility. You are not running the same scenarios every time, you are adapting to what changed:
Deployed a payment fix? Grab checkout tests from the e-commerce app and auth tests from the user service.
Updated the API? Pull relevant integration tests from three different feature areas.
Friday afternoon deployment? Run your “sleep well tonight” selection of critical path tests.
With QA flow’s smart execution logic working in the background, you focus on what to test, not how to organize it.
Efficient QA, exactly when you need It
The best tools adapt to your workflow, not the other way around. Whether it’s smoke tests, quick regressions, or isolated checks before a hotfix. Cherry-picking gives you the flexibility to test smart, not hard.
Because sometimes, you don’t need a full suite. You just need the right tests, right now. Click here to see how it works.