Format of workshop

[hnformentin]

(0) Before the workshop:

• Send out email with invitation and requirements, should be the organizer for breakout rooms. For example:

Dear XX team,

you are hereby invited to sign up for the half-day workshop on Tests and Test Driven Development next week:

What: Workshop in Tests and TDD
When: date, XX00-XX00
Where: Teams
By: Name

This is a course developed by Helena (with some help and feedback from Lars Kåre Skjørestad and the teams that already participated, and inspiration on Olve's talks and courses).

Prerequisite for the course:
- https://github.com/equinor/tdd_workshop/issues/7

In addition we require the following for attending the workshop:
- you have some experience using GitHub and git, and Visual Studio Code
- you also know how to use git, ssh, ssh-keygen from the command line
- particularly motivated for learning and sharing on tests and TDD

While not required (we will learn), it would be an advantage if you already have experience with:
- how to work with GitHub Actions and create deployment pipelines

If many people sign up we might have to split the class. Also, if this course is a success, then we will run it again with other teams! At the same time, we do a lot of group work where everyone helps each other so anyone satisfying the prerequisites for the course are very welcome to join us. This is going to be fun!

Sign up by sending a reply to this email.

Kind regards,

(1) Introduction and round to share the group experience (name, current software, e.g. package, web application, ..., experience with test?)

• up to 5 min per person if experienced group (use mouse to point who is next for larger groups)
• workshop organizer is the last
• highlight:
  -- the moderation role and disclaimer
  -- we drive on the same bus, the participants are to share screen often to solve problems together
  -- feedback is welcome in "Feedback - Workshop XX.XX.2021"
  -- Slack channel #tdd-test-driven-developement

(2) Check requirements for all (1h)

• Ask for a confirmation that each step is checked (e.g. in Slack #tdd-test-driven-developement)
• Have some colleague helping out in case the problem can not be solved in the session together

(3) Present Red-Green-Refactor (RGR, 10 min)

• ask someone to share the screen on the tests already available
• practice RGR on the easy example (2 RGR cycles)
• make a PR (check failing in the pipeline)

(4) Break/catch-up (15 min)

(5) Discuss theoretical part of the topic (15-20 min)

• all contribution and questions are welcome

(6) Break-out rooms (2 or 3 person peer-programming together)

• 45 min (1 or 2 RGR cycles, commit, push a PR from origin)
• First issue Create a method that sums two numbers in a string #8

(7) Discussion (30 min)

• Group by group, share screen
• Anyone need to catch-up?

(8) Break (15 min)

(9) Break-out rooms (different 2 or 3 person peer-programming together)

• 45 min (1 or 2 RGR cycles, commit, push a PR from origin)
• Second issue Support empty strings and single values strings #9

(10) Feed-back time (10 min)

• Fill feed-back form

(11) Conclusion (5 min each)

• What did you learn today?

Expected time: 4h15min + 10 min*participant

Update interesting discussions and share material in #tdd-test-driven-developement.