Optivem Training

Acceptance Test Driven Development (ATDD) in Legacy Code - Training

Prerequisites

• Medior / Senior Developer experience

Outline

• System Level Tests

  • Smoke Tests

  • E2E Tests

  • Acceptance Tests

  • External System Contract Tests

• Pipeline Architecture to support System Level Tests

  • Commit Stage

  • Acceptance Stage

  • Release Stage

• System Level Testing in Legacy Code

  • Pipeline Architecture in Legacy Code

    • Introducing Commit Stage

    • Introducing Release Stage

    • Introducing Acceptance Stage

  • Introducing E2E Testable Architecture

  • Writing Smoke Tests & E2E Tests

  • Introducing Acceptance Testable Architecture

  • Writing Acceptance Tests & External System Contract Tests

• Acceptance Test Driven Development (ATDD)

  • User Stories with testable Acceptance Criteria

  • Collaborative relationship between PO, QA & Developers

  • ATDD cycle - Acceptance Criteria & Acceptance Tests

Schedule

• Duration: 2h

Component Test Driven Development (TDD) in Legacy Code - Training

Prerequisites

• Acceptance Test Driven Development - Training completed

Outline

• Component Level Tests

  • Component Tests

  • Contract Tests

• Pipeline Architecture to support Component Level Tests

  • Commit Stage

• Component Level Testing in Legacy Code

  • Pipeline Architecture in Legacy Code - Commit Stage

  • Introducing Component Testable Architecture

  • Writing Component Tests & Contract Tests

• Component Test Driven Development (CTDD)

  • Decomposing Acceptance Criteria behavior into Component behavior

  • Translating failing Acceptance Test into Component Tests

  • Double Loop Development driven by Acceptance Tests & Component Tests

Schedule

• Duration: 2h

Unit Test Driven Development (TDD) in Legacy Code - Training

Prerequisites

• Component Test Driven Development - Training completed

Outline

• Unit Level Tests

  • Unit Tests

  • Narrow Integration Tests

• Pipeline Architecture to support Unit Level Tests

  • Commit Stage

• Unit Level Testing in Legacy Code

  • Introducing Hexagonal Architecture

  • Writing Unit Tests 

  • Writing Narrow Integration Tests

• Test Driven Development (TDD)

  • Decomposing Component behavior into Unit behavior

  • Test Driven Development (TDD)

  • Triple Loop Development - Acceptance Tests, Component Tests, Unit Tests

Schedule

• Duration: 2h

Modern Automated Testing - Training

Prerequisites

• Medior / Senior Developer experience

Outline

• Modern Test Pyramid

• System Level Tests

  • Smoke Tests

  • E2E Tests

  • Acceptance Tests

  • External System Contract Tests

• Component Level Tests

  • Component Tests

  • Contract Tests

• Unit Level Tests

  • Unit Tests

  • Narrow Integration Tests

Schedule

• Duration: 2h

Automated Testing in Legacy Code - Training

Prerequisites

• Modern Automated Testing Training was completed

Outline:

• Designing Pipelines to support Automated Testing

  • Commit Stage - Component Level & Unit Level Tests

  • Acceptance Stage - System Level Tests

  • Release Stage - Smoke Tests

• System Level Testing in Legacy Code

  • Introducing E2E Testable Architecture

  • Writing Smoke Tests & E2E Tests

  • Introducing Acceptance Testable Architecture

  • Writing Acceptance Tests & Contract Tests

• Component Level Testing

  • Introducing Component Testable Architecture

  • Writing Component Tests & Contract Tests

• Unit Level Testing

  • Introducing Unit Testable Architecture

  • Writing Unit Tests & Narrow Integration Tests

Schedule

• Duration: 2h

TDD in Legacy Code - Training

Prerequisites:

• Automated Testing in Legacy Code Training was completed

Outline:

• TDD - System Level

  • Acceptance Tests & Contract Tests in Legacy Code

  • Acceptance Test Driven Development (ATDD)

• TDD - Component Level

  • Component Tests & Contract Tests in Legacy Code

  • Component Test Driven Development (CTDD)

  • Double Loop Development

• TDD - Unit Level

  • Unit Tests & Narrow Integration Tests in Legacy Code

  • Test Driven Development (TDD)

  • Tripe Loop Development

• TLD vs TDD

Schedule

• Duration: 2h

Administrative Notes

• During sessions, there is 5 min break at end of each 1hr

• At the start of any sessions, the host can start the recording, if they want to save the training for future internal reference.

Training Reservations

1. Internal Website Access: After our introductory call, I'll send an email with a link to this internal website.

2. Invoice Details: You'll need to confirm number of participants for training, so that I can calculate the price. Also you'll need to provide company details so that I can send an invoice for advance payment.

3. Slot Reservation: Reserve a training slot here https://calendly.com/valentinajemuovic/training 

4. Calendar Event: Make a booking in your company calendar:

   1. Use some video conferencing tool - e.g. Zoom / Google Meet / MS Teams / etc. (whatever your company uses)

   2. Add Valentina Jemuović (valentina.jemuovic@optivem.com) as a required participant

   3. Add required participants (max number as in the invoice)

   4. Optionally, you can add the Engineering Leader (typically the CTO / Engineering Manager who contacted me) as an additional optional participant

   5. Generally companies want to record these sessions. In that case, in advance, please ensure that the meeting host knows how to record

Group Subscriptions

1. Purchase a group subscription

2. Download the invoice https://support.substack.com/hc/en-us/articles/360037489832-How-do-I-get-an-invoice-for-my-subscription 

3. Manage group members

Engineering Leadership 

• As an Engineering Leader, follow these steps to introduce the initiative & the sandbox project.