See what a QA Boutique PR audit looks like.
This example shows the type of concise report we send back after reviewing one public GitHub pull request: risk summary, findings, and regression tests your team can add or adapt.
Submitted PR
Update pricing component
Area
Pricing / billing
Preferred stack
Playwright
Repository access
Public GitHub PR
Output
Report + reply draft
// Pricing_new.tsx
const [selectedPlan, setSelectedPlan] = useState('sandbox');
const [isAnnual, setIsAnnual] = useState(false);
function calculatePrice(monthlyPrice: number) {
return isAnnual ? Math.floor(monthlyPrice * 0.8) : monthlyPrice;
}
<button className="subscribe-button">
Subscribe to {plans.find(p => p.id === selectedPlan)?.name}
</button>QA Boutique found
The pricing UI lets the user select a plan, but this PR does not show how the selected plan and billing mode are passed into checkout. This may be incomplete implementation, or the checkout logic may live elsewhere.
The annual toggle applies a monthly-equivalent discount, but the UI should clearly explain whether users see a monthly equivalent, annualized monthly price, or final annual total.
The selected plan and billing mode should be passed into checkout or onboarding in a way that can be tested, so the pricing flow does not silently regress later.
Suggested regression tests
Verify monthly vs annual pricing updates correctly for paid plans.
Verify Subscribe passes selected plan ID and billing mode into checkout.
Verify the free/Sandbox plan does not enter a paid checkout flow.
Example reply draft
Thank you for submitting this PR. The pricing component has clean UI and correct annual discount math, but the Subscribe button lacks a visible checkout handler—it's unclear whether clicking it initiates payment or persists the billing mode to the backend. I recommend adding a test that verifies the Subscribe button triggers checkout with the correct plan ID and billing mode, and another that confirms the annual toggle persists through to payment. Let me know if the checkout handler is implemented elsewhere or if you'd like me to review the full flow.
Want this for your PR?
Submit one public GitHub PR and we will send back a concise audit report plus regression-test ideas. For private repositories, sign in and connect only the repositories you choose.
Request a free PR audit