Workshop · Quality & releases · 4 days
Test automation in legacy systems
Four days to get tests into code that grew over years, without rebuilding it first.
- Duration
- 4 days
- Format
- On site at your office, in German or English
- For
- Developers and QA engineers working on an established system
- Prerequisites
- Experience in the system's programming language. Access to its code and build.
What your team takes away
- Tests for the riskiest parts of your system, written during the workshop
- A test suite that runs on every change and stops a faulty release
- A team that can keep extending the tests without us
Agenda
- Day 1
Getting a foothold
- Characterization tests that record what the code does today
- Finding seams in code that was not built for testing
- Test data and test environments
- Deciding what to test first, by risk
- Day 2
Backend tests
- Unit and integration tests with JUnit and Spring Boot
- Testing against a real database instead of mocks
- Testing the interfaces to other systems
- Keeping tests fast and independent
- Day 3
Process and UI tests
- Testing BPMN processes path by path
- End-to-end tests through the user interface
- Stable tests instead of flaky ones
- What not to test through the user interface
- Day 4
Into the pipeline
- Running every test on every change
- Quality gates: what blocks a release and what does not
- Coverage that means something
- Handing the test suite over to your team
In your code
The tests your team writes during the course stay in your repository and run in your pipeline. Nothing is rebuilt first: the course starts with the code as it is.
Where this comes from
The approach comes from the test suites behind more than 4,000 production deployments since 2019, without a single rollback.
Request this workshop
You receive an offer with proposed dates within two working days.