Chilean craft beer discovery platform, product and quality
Figures as of November 2026
Co-founder covering product management and quality on a 3-person team, from risk-based test planning to a new end-to-end automation base.
- Role
- Co-founder, Product Owner and QA Lead
- Timeline
- 2026 to present
- Stack
- Next.js 15, TypeScript, MongoDB, Better Auth, Playwright
- Note
- The application code was built by my partners; my work was product management, testing and tool decisions.
The problem
A web platform to discover Chilean craft beers, bars and breweries on an interactive map was heading to launch with no formal testing, no analytics and no official email. Nobody on the team owned product or quality.
Discovery
I reviewed the state of the project against the plan: I analyzed a recorded team meeting of almost two hours together with the brand brief and the project board, and listed what the team believed was ready versus what was actually built. The main gaps: no tests, no analytics and no email on the project's own domain.
Key decisions
- ▹Test the riskiest areas first. Accounts and role-based permissions carry the highest risk, so they came first.
- ▹AI executes, a human verifies. AI agents ran test sessions in parallel; I designed the plan, reviewed the test cases, verified every defect manually and wrote the reports. Manual verification caught a defect the automated runs missed: a dialog hidden behind the map.
- ▹Simple tools with clear limits. For analytics I recommended a free tool with a documented limit (Umami) over a more complex one, to reduce setup work and privacy risk before launch.
What I built
- ▹A risk-based test plan. Full-site scope is estimated at 670 to 850 test cases across 12 areas.
- ▹Two test cycles: 144 test cases executed (156 executions including 12 re-tests) and 24 defects reported (1 high, 10 medium, 13 low) in ISTQB-style reports.
- ▹Coverage of the highest-risk areas: account and authentication 69 of about 90 cases; age and role permissions 75 of about 110.
- ▹An end-to-end automation base with Playwright, set up from scratch: Chilean locale and time zone, integration with the development server, first tests passing. Of the full scope, 281 scenarios are selected for automation and being implemented now.
- ▹A tool decision document for analytics and domain email, plus the team's meeting minutes with owners and next steps.
Status and results
Pre-launch. Testing campaign ongoing and automation of the 281 selected scenarios in progress. Security findings are shared privately with the team.
What’s next
Finish automating the selected scenarios, cover the remaining areas (brewery dashboard, discovery and map, moderation) and run a regression cycle before launch.