Plan capacity for automated regression testing against measured growth rather than optimism.
Designing Automated Regression Test Plans for Large Systems
Move automated regression testing from general awareness to a repeatable, reviewable practice.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Systems supporting automated regression testing fail in ways that are obvious afterwards and invisible before. Technical debt in the wider technology and systems delivery agenda is borrowed against future delivery capacity, at compound interest. They gain the ability to sequence improvements to this strand of technology and systems delivery in an order their organisation can absorb. It is written for people who have to make automated regression testing work with the resources they already have. Participants apply the practice within technology and systems delivery to their own technical platform throughout, so the output is directly usable. The course sets out a working method for the technology and systems delivery discipline that participants can apply the week they return. Ambition around automated regression testing outruns capacity unless the sequencing is deliberate. Practitioner evidence points the same way: this strand of technology and systems delivery improves fastest where responsibility for it is named and owned. The programme ends where implementation begins, with the technology and systems delivery capability broken into steps someone can start on Monday.
Expected Learning Outcomes
Document automated regression testing to the level a new engineer could operate it.
Distinguish the parts of automated regression testing that must be standardised from those that require judgement.
Define the availability, performance and recovery targets for automated regression testing.
Build a register of the risks attaching to automated regression testing and keep it current.
Secure the software supply chain and dependencies within automated regression testing.
Plan the handover of automated regression testing so that capability is not lost when key staff move on.
Who Should Attend
Software engineers and technical leads building automated regression testing.
Information security specialists protecting automated regression testing.
Quality staff verifying that automated regression testing performs as designed.
Managers with direct responsibility for automated regression testing within the technical platform.
Database administrators managing data within automated regression testing.
Quality and test engineers verifying automated regression testing.
Course Modules
Automated regression testing: change control and rollback
2 sessions · 8 pointsSession 1Documenting automated regression testing so someone else can operate it
- Run a load test on automated regression testing at expected peak plus a margin.
- Confirm the support model and escalation path for automated regression testing.
- Confirm that those complying with automated regression testing understand why it exists.
- Identify where judgement in automated regression testing is legitimate and where it is not.
Session 2Least privilege in automated regression testing without blocking the work
- Confirm data retention and deletion rules applied within automated regression testing.
- Arrange the handover of automated regression testing so capability survives staff changes.
- Set the review interval for automated regression testing and who attends.
- Assess the exit route from any cloud or vendor dependency in automated regression testing.
Automated regression testing: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Moving automated regression testing from approval to execution
- Define incident severity levels for automated regression testing and the response each triggers.
- Verify six months later that changes to automated regression testing have held.
- Rehearse the briefing on automated regression testing that would follow an incident.
- State the availability and recovery objectives for automated regression testing as numbers.
Session 2What has to be agreed before work on automated regression testing starts
- Establish who is informed, consulted and accountable in automated regression testing.
- Test the failover for automated regression testing rather than assuming it works.
- Close out actions on automated regression testing rather than leaving them open indefinitely.
- Review access rights on automated regression testing and remove what is no longer needed.
Automated regression testing: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Sizing capacity for automated regression testing on measured growth
- Build the internal briefing that explains automated regression testing to those affected.
- Identify the single points of failure in automated regression testing.
- Measure current load on automated regression testing and project it forward twelve months.
- Record the technical debt in automated regression testing and schedule repayment.
Session 2Making releases of automated regression testing routine instead of risky
- Assign responsibility for keeping documentation of automated regression testing current.
- Collect evidence on the present handling of automated regression testing before proposing changes.
- Document the runbook for automated regression testing to the level a new engineer could use.
- Review logging on automated regression testing for coverage and retention.
Automated regression testing: requirements, targets and service levels
2 sessions · 8 pointsSession 1Where automated regression testing typically breaks, and why
- Confirm every release of automated regression testing can be rolled back within a defined time.
- Check that automated regression testing still works when volumes rise unexpectedly.
- Prepare the response for the most likely failure in automated regression testing.
- Confirm that contractual obligations around automated regression testing are understood.
Session 2Designing automated regression testing around how it will fail
- Configure alerting on automated regression testing that reflects what users experience.
- Agree what will be standardised in automated regression testing and what will not.
- Compare the cost of automated regression testing with the cost of its absence.
- Inventory third-party dependencies inside automated regression testing and their update status.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.