Case QA · Automation
QA and automation across three teams
Three different contexts (a retail SaaS, a health research institute and a European project) and the same method: build the regression suite, keep it alive in the pipeline and automate whatever eats the team's time. It is internal work for each company, so I show no screenshots: I do show what I did and with what.
Three teams, one method
- 012026
Accenture · UPRO platform (Red.es)
A platform with European funding: data collection was done by hand and the team needed support and documentation.
- Automated part of the data collection with Playwright and wrote scripts inside Excel to process and move the data.
- Functional support, ticket management and an internal documentation tool for me and my colleagues.
- Playwright
- JavaScript
- Excel
- Support
- 022024 – 2025
VHIR · Vall d'Hebron Research Institute
Health research: every deployment had to be validated without breaking anything.
- E2E regression suite with Cypress and Playwright, integrated into the Bitbucket Pipelines CI pipeline.
- Technical documentation of the QA process and, when the project closed, a month of validation and E2E tests on the UAB languages platform.
- Cypress
- Playwright
- Bitbucket Pipelines
- Docker
- 032022 – 2024
Stockagile · retail SaaS
Inventory management with continuous release cycles and a small team.
- Manual and automated testing with Cypress and regression plans per version.
- Bug reporting and QA documentation alongside the development team, in an agile setup.
- Cypress
- Postman
- Jira
- Docker
01 The challenge
Teams without an established QA process that needed to stop regressions without slowing releases down.
02 What I did
- Built E2E regression suites with Cypress and Playwright, integrated in the CI pipeline with Docker.
- Designed cases and scenarios, reported bugs through to closure and tested APIs with Postman when needed.
- Automated manual chores (data collection, Excel transfers) and documented the process for the team.
03 Result
- Reusable suites that validated every deployment in the pipeline and a documented QA process that stayed with the team.