Checks the build against the plan.
Paco reads the code against every requirement and acceptance criterion. A green build is not enough if the work missed what the team actually decided to ship.
QA with Paco
QA with Paco.
Prove the change. Then protect everything around it.
Paco reviews every change before it ships. He reads the ticket the change came from and the code that implements it. He checks the change against what it was supposed to do, against the standards your team already follows, and against the parts of the app it was not supposed to touch.
More importantly, Paco opens the app, walks the flow the way a user would, and captures what he sees. When something breaks, the report names what failed. That is the difference between a review that says the code looks right and one that says the feature works.
How It Works
Main features
Uses the product like a person would.
He opens the app in a browser and works through real scenarios, not just unit tests. Each pass is documented with the evidence and screenshots your team needs to review it.
Looks beyond the new release.
Paco rechecks the flows nobody thought to touch, so regressions from the last release surface before customers find them. QA covers the product around the change, not only the change itself.