Designing Comprehensive Automated Software Testing Strategies

Develop the judgement and the documentation needed to run automated software testing properly.

📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

Availability targets for automated software testing are commercial commitments, whatever the engineering team calls them. Most outages involving this strand of technology and systems delivery are triggered by a change somebody considered routine. Applied research in technology and systems delivery consistently shows that early structure around this part of technology and systems delivery reduces downstream rework. The programme converts automated software testing from an area of general awareness into a set of repeatable practices. Participants gain a realistic view of what the wider technology and systems delivery agenda costs and what it returns. What blocks progress on the technology and systems delivery discipline is usually unclear ownership rather than unclear intent. Each session closes with a decision the participant must justify about automated software testing in their own setting. Participants come from operational and oversight roles, and both perspectives on this part of technology and systems delivery are used deliberately. The closing exercise tests whether the participant's plan for this aspect of technology and systems delivery survives a hostile question.

Expected Learning Outcomes

01

Manage change to automated software testing so every release can be rolled back.

02

Reduce avoidable variation in how automated software testing is carried out across teams.

03

Build the deployment pipeline for automated software testing so releases are routine rather than events.

04

Identify the failure points in automated software testing most likely to cause loss, and control them first.

05

Design the architecture of automated software testing around its failure modes, not only its happy path.

06

Diagnose whether a problem in automated software testing is one of design, resourcing or discipline.

07

Secure the software supply chain and dependencies within automated software testing.

Who Should Attend

01

Project managers delivering changes to automated software testing.

02

Experienced practitioners formalising an approach to automated software testing that has grown up informally.

03

Infrastructure and platform engineers operating automated software testing.

04

Procurement and contracting staff whose agreements set obligations around automated software testing.

05

Quality and test engineers verifying automated software testing.

06

Information security specialists protecting automated software testing.

Course Modules

01

Automated software testing: incident response and severity

2 sessions · 8 points

Session 1The paperwork for automated software testing that is actually needed

  • Name a single owner for each element of automated software testing.
  • Confirm every release of automated software testing can be rolled back within a defined time.
  • Run a load test on automated software testing at expected peak plus a margin.
  • Restore a backup of automated software testing in a test environment and time it.

Session 2Monitoring automated software testing from the user's point of view

  • Document the runbook for automated software testing to the level a new engineer could use.
  • Review logging on automated software testing for coverage and retention.
  • Test the failover for automated software testing rather than assuming it works.
  • Set out how exceptions to automated software testing are requested and approved.
02

Automated software testing: monitoring, alerting and observability

2 sessions · 8 points

Session 1What has to be agreed before work on automated software testing starts

  • Assess the exit route from any cloud or vendor dependency in automated software testing.
  • Confirm that those complying with automated software testing understand why it exists.
  • Set delivery and reliability indicators for automated software testing the team trusts.
  • Write down the assumptions underpinning the approach to automated software testing.

Session 2Proving the backup of automated software testing by restoring it

  • State the availability and recovery objectives for automated software testing as numbers.
  • Confirm that contractual obligations around automated software testing are understood.
  • Apply change control to automated software testing including emergency changes.
  • Close out actions on automated software testing rather than leaving them open indefinitely.
03

Automated software testing: architecture and designing for failure

2 sessions · 8 points

Session 1Documenting automated software testing so someone else can operate it

  • Establish who is informed, consulted and accountable in automated software testing.
  • Arrange the handover of automated software testing so capability survives staff changes.
  • Set out the decisions in automated software testing that require sign-off and by whom.
  • Reduce the variation in how automated software testing is carried out between teams.

Session 2Retiring the legacy part of automated software testing

  • Configure alerting on automated software testing that reflects what users experience.
  • Review access rights on automated software testing and remove what is no longer needed.
  • Set the review interval for automated software testing and who attends.
  • Collect evidence on the present handling of automated software testing before proposing changes.
04

Automated software testing: build, pipeline and release discipline

2 sessions · 8 points

Session 1Building lasting competence in automated software testing

  • Confirm the support model and escalation path for automated software testing.
  • Measure current load on automated software testing and project it forward twelve months.
  • Inventory third-party dependencies inside automated software testing and their update status.
  • Benchmark the organisation's automated software testing against comparable operations.

Session 2Setting availability and recovery targets for automated software testing honestly

  • Confirm data retention and deletion rules applied within automated software testing.
  • Record what was learned when automated software testing did not go as planned.
  • Agree the indicators that will show whether automated software testing is improving.
  • Prepare the response for the most likely failure in automated software testing.

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.