QA and test automation
Test automation means that critical paths in an application, such as cart to payment, are checked by a machine before every deployment. We write E2E tests in Playwright, wire them into CI and you get a report after every build. Time to the first tests: 1—2 weeks.
- Typical first deliverable
- automated tests of critical flows in CI, a report after every build
- Delivery
- 1—2 weeks
- Entry price
- from €900
- Stack
- Playwright · Repeato · Jira · Jenkins · Octopus Deploy
What we cover
E2E tests of critical paths
Login, order, payment and the other steps that must not break.
CI/CD integration
Tests run before every deployment, for example in Jenkins with Octopus Deploy.
Manual testing
Bug reporting in Jira where automation is not enough or does not pay off.
A report after every build
The team sees what passed and what failed right after the build.
When it pays off
- Every release is stressful and the fixes come after it.
- Your customers report the bugs.
- Manual regression testing takes days and slows releases.
- Developers do not have time to test their own changes.
When it does not pay off
- A small site that changes once a year.
- An application whose main screens are still changing fundamentally. Tests would need constant rewriting.
What is included
- E2E tests of critical paths — from cart to payment
- Wired into CI so the tests run before every deployment
- Manual testing and bug reporting where automation is not enough
- A report after every build, not once a quarter
How it works
- Choosing critical paths
We decide what would cost the company most if it stopped working.
- First tests
We cover those paths with E2E tests in Playwright.
- CI integration
Tests run before every deployment and block a faulty release.
- Maintenance
Tests grow with the application and you get a report after every build.
How much test automation costs
Test automation starts from €900 excluding VAT. The price depends on the number of critical paths and on whether the application has a test environment and stable data. We extend coverage by risk, not by the number of screens.
Frequently asked questions
What should be tested first?
The paths that bring money or would stop operations: login, order, payment, the main processes in an internal system. Edge features can wait.
Will automated tests replace manual testing?
Not entirely. Automation guards what already worked. New features, usability and unusual situations are checked by a person.
Can you test an application built by another supplier?
Yes. E2E tests work with the application as a user does, so they do not need its code. We need a test environment and access.
Related
- Process automationSystems hand data to each other — no retyping
- Websites and e-commerceOne measurable goal, a fast site, a clear CTA
- Custom applicationsInternal systems and portals from prototype to production
- AI solutionsDocuments, enquiries, classification — with error checking
- Analysis and specificationA specification you can genuinely build from
- AI coding changes hiring: weekly briefing, November 2, 2026Blog
- Automatic Payment Matching in SuperFaktúra: A Practical GuideBlog
- Excel replacement for business: when to build a custom appBlog