Skip to content
PinePoint
Test a PR

QA agents for every pull request

Find the break.Open the bug.

Ten simulated users test your preview in real browsers. When something breaks, step into the session and see it for yourself.

Test a PR See it in action

For the code you ship. And the bugs you don’t see.

PR #10 · Add free shippingDemo
preview / cart Finding captured
Demo store cart showing SAVE10 applied twice and an incorrect total of $19.44.
Same coupon. Second discount.

One coupon. Two discounts.

Found by the coupon tester

Expected$21.60
Preview$19.44

Interactive example · recorded demo screenshot

The context comes with the finding.

Example finding / PR #10

The coupon applies twice.

Recorded browser screenshot: SAVE10 is applied twice. The cart total is $19.44 instead of $21.60.

Follow the evidence.

  1. Add a sage linen apron.
  2. Apply SAVE10.
  3. Apply SAVE10 again.

This is a recorded example. In a live run, a retained session lets you inspect the browser and take control.

Explore the sample dashboard

A new perspective.
Right in your workflow.

GitHub PR Vercel preview Pine Computers

01 / Find the break

One preview.
Ten fresh perspectives.

The first-time buyer. The keyboard user. The person who applies a coupon twice. Different missions find different ways to break your changes.

One preview. Ten perspectives.Linen & Oat · demo store
Illustrative demo
Keyboard shopperQueued
Cart explorerQueued
First-time buyerQueued
Shipping checkQueued
Empty cartQueued
Order flowQueued
Mobile shopperQueued
Coupon stackingQueued
Returning shopperQueued

Start with the changes in your PR.

Planned from your diff and qa.md. Tested through Flow, UI, Abuse, Access, and Safety lenses.

02 / Open the bug

The moment it broke.
Ready for a closer look.

Open a retained live session from the finding. Inspect the cart, the inputs, and the browser that found the problem. Take control when you need to.

Explore the sample dashboard

Sample data · no live run required

PinePoint reviewExample
PinePointFound on the PR preview

SAVE10 applies twice.

Expected $21.60. Saw $19.44.

  1. Add a sage linen apron.
  2. Apply SAVE10.
  3. Apply SAVE10 again.
Screenshot. Steps. A link to the session.
A proposed fix, for your review
if (cart.coupons.includes(code)) {
  return { cart, message: "Coupon already applied." };
}
01

Evidence you can inspect.

Screenshots and short steps show what happened. Rechecks help separate bugs from noise.

02

You make the call.

Mark Bug or Not a bug. PinePoint keeps the decision with the finding and on the PR.

03

A fix you can review.

Get a proposed code change. Read it, post the suggestion, and commit it when you’re ready.

A few good questions

Before your
first run.

Do I need to write a test suite?

PinePoint reads the PR diff and your qa.md, then plans ten missions for the preview. Each simulated user explores one goal in its own browser. Your existing tests still have their place; PinePoint adds another look at the running product.

How does PinePoint check a finding?

Failed preview missions are checked again and compared with production when applicable. Confirmed bugs, possible issues, and existing production bugs get different labels, so you can see what the evidence actually supports.

Will it change my code?

You make the decision. When you mark a confirmed finding as a bug, PinePoint can propose a fix. You review it and choose whether to post it as a GitHub suggestion. You commit the change yourself.

What can I try today?

The current MVP tests GitHub pull requests with Vercel previews. Start with the sample dashboard or the demo PR to explore the workflow. A dedicated rerun of a failed mission after a fix is still in development.

Your next PR has company

A QA team for
what you ship next.

Test a PR See the demo PR

Real browsers. Clear evidence. Your decision.