World's Best Intro to TDD (Test driven development)
WHEN: 25 of OCTOBER, 2019
VENUE: Vilnius (will be announced)
EARLY BIRD (till 1st of OCT):
299€ (+ VAT)
399€ (+ VAT)
You can register to the training by filling the registration form. If you have any questions, contact us: firstname.lastname@example.org
Join J. B. Rainsberger and learn whether test-driven development (TDD) will work for you. In addition to learning the steps of TDD, this course unlocks some of the secrets of modular design from one of TDD’s master practitioners. Bring your laptop and be prepared to change the way you write software.
You have had professional experience on at least one software project. You would like to know how to design software incrementally with test-driven development. You don't need any prior experience with TDD.
In this 1-day workshop, you will learn enough to decide whether you should adopt TDD as a daily practice in your work. You will also learn enough to start using TDD to fix defects and build features.
- how to practise TDD differently for your needs
- how TDD can help you deliver features more steadily to delight your project managers and customers
- how TDD can help you protect your long-term capacity to write code
- the Simple Design Dynamo and how it helps you make design decisions
- how practising TDD can help anyone become a trusted designer, even a so-called "architect"
- how use to test doubles (mock objects) effectively! (Yes, it's possible!)
- How to adopt TDD safely and effectively
- Realizing the promise of modular design with TDD
- How the Simple Design Dynamo helps you evolve the architecture of an application
- How to avoid the trap of a large, slow test suite
- Your questions on how to take the next steps to practise TDD
Before the Workshop
Bring a computer to the workshop prepared to write code in any programming language that you like. Install a testing framework (such as JUnit, Jasmine, or RSpec) and learn how to write and run one failing test before you arrive. Create an empty project with a version control repository (like git, darcs, hg, or bzr) and set up the "ignore" file so that you only commit source files to version control. You can use a resource like https://gitignore.io to help you do this last part. If you can commit a failing test to version control and run tests with a single command (in your shell or your IDE), then you're ready to start!