Gojko Adzic's Test Driven .NET Development in Practice

This course teaches the basic Test Driven Development practices including unit testing, refactoring and acceptance testing. By applying these practices, you will be able to build quality into software from the start, design and develop systems fit for purpose and write code that is easy to maintain and evolve in the future.

The is a completely hands-on course with practical workshops straight from the start, interrupted by very short presentations to explain the practices and put things into a wider perspective. It is based on the latest tools and current knowledge and ideas from the community, so you'll be practicing the state of the art.

LEARN HOW TO:

* Design and develop software driven by tests
* Protect software from unwanted changes using regression tests
* Evolve software design with refactoring and TDD
* Recognise smells in the code and clean them up
* Capture requirements and specifications as acceptance tests
* Use executable specifications to drive development
* Continuously integrate software to get quick feedback about changes
* Apply best practices and avoid pitfalls of unit and acceptance testing
* Use MBUnit, Gallio, Rhino Mocks and FIT.NET

WHAT, WHEN, WHERE
This course will be delivered by Gojko Adzic at Skills Matter in London, on Dec 1-2nd 2009. Gojko is also the author of this course. Only 16 places available, so if you would like to come to this course, get your skates on and register here:
http://skillsmatter.com/course/open-source-dot-net/test-driven-dot-net-development-in-practice/wd-41

PROGRAMME
Day 1

* Introduction to TDD
* Unit testing basics
* Using TDD with MBUnit to explore and design software
* Writing efficient unit tests
* Applying mock and stub objects with Rhino Mocks to isolate tests
* Best practices and pitfalls of unit testing

Day 2

* Identifying code smells and improving the code with refactoring
* Continuous integration and detecting change
* Converting requirements into executable specifications
* Applying agile acceptance testing with FIT.NET
* Best practices and pitfalls of acceptance testing

• < Previous Event
• Next Event >

Comment