> Markdown version of [/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly?t=1204](https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly?t=1204). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# How to add test automation to your project: The good, the bad, and the ugly

Test automation is not a spare-time activity. Discover how to avoid hidden implementation traps, align tools with team skills, and treat test scripts as first-class code.

- **Speakers:** [Augustin Gottlieb](https://www.wearedevelopers.com/@augustin-gottlieb)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 26:20
- **URL:** https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly

## Summary

Transitioning a project from manual testing to end-to-end test automation requires a cultural shift alongside technical implementation. Integrating automation addresses regression testing bottlenecks by enabling faster feedback loops through continuous integration pipelines and team-visible dashboards. Beyond raw speed, automation acts as a catalyst for collaboration, bridging the gap between developers and QA through pair testing and shared responsibility for system quality. By automating critical bugs and repetitive checks, QA professionals reclaim time for nuanced, high-value exploratory testing.

Successful adoption requires avoiding common implementation traps like the spare time fallacy. Test automation cannot be a side task; it must be explicitly estimated within sprint planning and integrated directly into the Definition of Done. Teams must also anticipate the hidden costs of automation by reserving dedicated time—often up to 50% of an effort—for maintaining test suites and addressing technical debt. Crucially, testing scripts must be treated as first-class development code subject to rigorous pull request reviews, static analysis, and proper design patterns.

An automation initiative fails when treated as a silver bullet that ignores the human element of software delivery. Test managers must align framework choices with the team's existing technical competencies—such as leveraging Playwright if the team already excels in TypeScript—rather than forcing trendy tools that introduce friction. Managing stakeholder expectations requires ditching vanity metrics like total test count in favor of tracking escaped issues in production. Ultimately, building a sustainable automation strategy depends on fostering psychological safety so teams can openly surface environment blockers, refine prerequisites, and treat automation as an evolving product rather than a one-off project.

**Keywords:** end-to-end test automation, regression testing strategies, exploratory testing workflows, sprint effort estimation, agile definition of done, test code maintenance, qa and developer collaboration, pair testing methodologies, escaped issues metrics, test framework selection, continuous integration feedback loops, test environment management, software technical debt, psychological safety in engineering

## Chapters

1. **Defining the project setup for introducing test automation** (00:05) — Simulating a test manager's entry into a legacy mobile project clarifies the specific requirements for introducing end-to-end regression automation.
1. **Using test automation as a catalyst for team collaboration** (03:52) — Sharing quality ownership across the development team breaks down silos and improves testable architecture.
1. **Implementing faster feedback loops and mandatory automation checks** (07:57) — Making regression test status immediately visible and mandatory prevents teams from bypassing automated quality gates.
1. **Increasing confidence with automated coverage of critical bugs** (10:04) — Automating end-to-end tests for previously resolved bugs provides security and traceable proof of application stability.
1. **Freeing up bandwidth to prioritize exploratory testing activities** (12:00) — Shifting manual regression tasks to automated suites empowers testers to focus on creative exploration of edge cases.
1. **Avoiding the spare time fallacy in sprint planning** (14:54) — Estimating dedicated capacity for automation tasks and adding them to the definition of done ensures consistent progress.
1. **Accounting for test maintenance and enforcing code reviews** (17:28) — Allocating explicit effort for fixing technical debt and peer reviewing test scripts prevents automated suites from rotting.
1. **Establishing stable test environments and required test data** (20:04) — Preparing proper infrastructure and reliable data before writing tests prevents false positives and maintains organizational trust.
1. **Managing stakeholder expectations around test automation capabilities** (21:19) — Educating stakeholders that automation is not a silver bullet shields engineering from backlash when bugs inevitably escape.
1. **Aligning testing frameworks with team skills and feedback** (22:51) — Matching automation tools to existing developer proficiencies fosters psychological safety and accelerates framework adoption.
1. **Treating test automation as a managed software product** (24:51) — Starting with a clear scope and underlying strategy ensures the test suite directly delivers measurable product value.

## Related Moments

- [Shifting development challenges towards complex testing and team collaboration](https://www.wearedevelopers.com/videos/1459-the-evolving-landscape-of-application-development-insights-from-three-years-of-research) (from "The Evolving Landscape of Application Development: Insights from Three Years of Research")
- [Balancing automated checking with human-centric testing skills](https://www.wearedevelopers.com/videos/87-excellent-software-testing) (from "Excellent Software Testing")
- [Establishing core principles for successful test automation adoption](https://www.wearedevelopers.com/videos/100215-smart-test-automation-the-experience-of-legacy-transformation) (from "SMART Test Automation - the experience of legacy transformation")
- [Scaling automated testing practices across growing engineering teams](https://www.wearedevelopers.com/videos/662-write-tests-you-love-not-hate) (from "Write tests you love, not hate")
- [Introduction to keeping test code clean](https://www.wearedevelopers.com/videos/515-dirty-tests-and-how-to-clean-them) (from "Dirty Tests And How To Clean Them")
- [Convincing management to invest in automated testing](https://www.wearedevelopers.com/videos/541-tdd-for-vue-js-developers) (from "TDD for Vue.js Developers")

## Related Articles

- [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing)
- [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)
- [Integration And E2E Testing: Are They Complementary or Interchangeable?](https://www.wearedevelopers.com/magazine/86-integration-and-e2e-testing-are-they-complementary-or-interchangeable)
- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)

## Related Jobs

- [QA Automation Engineer](https://www.wearedevelopers.com/jobs/ext/1414297-qa-automation-engineer) at **Bitpanda**
- [Staff, Analytics Engineer](https://www.wearedevelopers.com/jobs/ext/569504-staff-analytics-engineer) at **Twilio**
- [Software Tester (f/m/d)](https://www.wearedevelopers.com/jobs/44712-software-tester-f-m-d) at **Power Plus Communications**
- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [Test Engineer](https://www.wearedevelopers.com/jobs/ext/1872489-test-engineer) at **ZEISS Group**
- [Softwaretester Embedded Linux Systems](https://www.wearedevelopers.com/jobs/ext/1432629-softwaretester-embedded-linux-systems) at **Power Plus Communications AG**