Customer story · Software
Automated tests on every merge, and a release process the whole team uses
47 automated tests that run in under three minutes on every merge, one test and release strategy for the whole team, and developers who now ship tests with every feature.
- Client
- A US software company building AI tools for the workplace
- Where
- United States, fully remote
Challenge
The starting point
The company builds AI-powered tools for digital workplaces. As the product grew, releases got slower and riskier: changes in one part of the system could break another, and nobody could say with confidence that a release was ready. They asked us to help, and the whole engagement ran remotely.
- No test automation framework. Quality depended on manual testing, which couldn't keep up with frequent updates.
- No clear workflow for verifying bug fixes, so fixed issues kept coming back.
- Testing without shared procedures or documentation, which made coverage hard to judge and new people slow to onboard.
- No acceptance test plan, so it was never quite clear when a feature was ready to release.
Approach
What we did
Tools
- GitHub Actions
- Playwright
- Bruno
- Python
- TypeScript
- A test pipeline in GitHub Actions for both frontend and backend, so automated tests run as part of every change.
- Automated API tests that check the backend does what the product documentation says it does.
- Automated frontend regression tests, so new changes don't quietly break what already works.
- Every test process written down, with our observations and recommendations for what to improve next.
- Exploratory testing alongside the automation, and reusable test assets the team can extend on their own.
Results
What changed
- A first suite of 47 automated tests that runs in under three minutes.
- The same tests run in development, pre-production and production.
- Tests run automatically on every merge.
- Developers learned to write testable code and now deliver tests with each feature and bug fix.
- The whole development team works to one test and release strategy.
- The team uses exploratory testing, with heuristics and charters, to find what scripted tests miss.
- More reliable deployments and fewer issues reaching customers.
“House of Test completely changed the way we develop by integrating a test automation framework into our existing pipeline. They also built a solid test and release process that was practical, effective, and tailored to fit our environment, product, and team. Alex and Andy quickly grasped the full context of our product within just a few days. They showed real initiative, creativity, and strong technical and communication skills, fitting right in with our team and jumping straight into the implementation phase of our project.”
The services behind this project
Facing something similar?
Tell us about your team and what you're working on. One of our engineers will get back to you.