What Will I Learn?
✓ Write Unit Tests
✓ Run and Debug Unit Tests
✓ Write Manual Mocks
✓ Write Mocks with Mocking Framework
✓ Practice Test-Driven Development (TDD)
✓ Apply Best Practices of Writing Unit Tests
Requirements
- You should already be familiar with the basics of C#
- You should already be familiar with the basics of unit testing
- You should already be familiar with the basics of dependency injection
Description
Today unit testing is the absolutely required skill which is required from any professional developer. Companies expect from developers to know how to write unit tests including all the most important topics such as mocking and test driven development (TDD in short).
This course is all about practicing TDD using C# programming language and NUnit as a unit testing framework. Along the way, we will learn the concepts related to unit testing. This course does not cover all the features of NUnit. This course is way more interesting.
Learning unit testing and TDD puts a powerful and very useful tool at your fingertips. Being familiar with unit testing and TDD you can write reliable and maintainable applications. It is very hard to lead a project which is not covered by unit tests.
Content and Overview
This course is primarily aimed at developers who’re already familiar with the basics of unit testing and dependency injection. Some experience in C# programming is required. The course provides solid theoretical base reinforced by tons of practical material.
We start with basics of test-driven development. Why we need TDD? What is TDD? When TDD fails, three laws of TDD, different types of tests, tooling and other fundamental topics. This section is mostly theoretical.
Theory is dead without practice, so starting from the second section, you’ll see tons of programming sessions where I’ll demonstrate how to implement generating of Fibonacci numbers, FizzBuzz, parsing of roman numerals, updateable spin synchronization primitives, tic-tac-toe or crosses and noughts game and game in sticks. You’ll also learn:
- How a regular agile development process looks like
- That you need to learn shortcuts to practice TDD more smoothly
- Three Main TDD techniques: faking, triangulation and obvious implementation
- Which tests to write first
- How to start writing a test in a TDD manner
- Stack kata
- Immutable stack kata
- And list kata
- What is acceptance testing
- About the SpecFlow acceptance testing framework
- How to write acceptance tests with SpecFlow in Gherkin language
- What are UI tests
- What tools for writing UI Tests exist
- How to access UI through the TestStack.White framework
Have you heard about katas? No, I’m talking about programming. In the third section, you’ll learn what is a code kata and I’ll demonstrate three code katas:
Growing an application by writing tests first, we’re not only writing unit tests first. So, in the next section, you’ll learn what is acceptance testing and integration testing. You’ll learn:
You’ll need to see how to apply all the material learned by this moment. Practice helps very much with understanding especially when we uncover highly practical topics such as TDD. That’s why I decided to show you how all the things work in practice altogether. So, in the next section, you’ll see a real enterprise approach for working on a software project in action.
- I’ll build a bridge to UI through TestStack.White applying the Page Object design pattern
- I’ll write acceptance tests using the bridge built for accessing UI
- I’ll implement ViewModels and all the corresponding business-logic
- What is TDD in the end? Is it possible to live without it?
- The relationships between TDD and Agile development process
- Should we design architecture upfront or not?
- Do unit tests guarantee the success?
- Quality of tests, some criterions
- How to express data for writing unit tests
- Shouldly for writing more readable assertions
- Singletons, Static classes and testability, Builder design pattern
- And some other important topics
The last two sections are rather philosophical. We will discuss:
- What is TDD in the end? Is it possible to live without it?
- The relationships between TDD and Agile development process
- Should we design architecture upfront or not?
- Do unit tests guarantee the success?
- Quality of tests, some criterions
- How to express data for writing unit tests
- Shouldly for writing more readable assertions
- Singletons, Static classes and testability, Builder design pattern
- and some other important topics
Here is my Teaching Approach –
No fluff, no ranting, no beating the air. I esteem your time. The course material is succinct, yet comprehensive. All important concepts are covered. Particularly important topics are covered in-depth. For absolute beginners, I offer my help on Skype absolutely free, if requested.
Take this course, and you will be satisfied.
Who is the target audience?
- Any developer who wants to improve professional programming skills
Curriculum
- Outline
- Why we Need TDD?
- What is TDD?
- Red / Green / Refactor
- Three Laws of TDD
- Changing Requirements and the Safety Net
- F.I.R.S.T.
- Code Coverage
- Different Types of Tests and TDD
- Testing Frameworks and Tools
- When TDD Fails?
- Conclusion
- Outline
- Regular Agile Process in 200 Words
- VS and R# Shortcuts
- Fibonacci Numbers
- Three Main TDD Techniques
- Grabbing the Gold
- FizzBuzz
- Reading Roman Numerals
- Updateable Spin
- Continuous Testing
- Tic-Tac-Toe (Crosses and Noughts)
- Assert First
- Demo – Sticks
- Conclusion
- Outline
- Stack Kata
- Immutable Stack Kata
- List Kata
- Conclusion
- Outline
- Problem Demo
- Refactoring to Make Code Testable
- Test Doubles
- Writing Tests with Hand-Rolled Mocks
- Mocking Frameworks
- Writing Tests with a Mocking Framework
- NSubstitute. Key Features
- Classic School vs London School
- Conclusion
- Outline
- What is an Acceptance Test?
- Overview of SpecFlow
- Gherkin. Features and Scenarios
- Basics of SpecFlow
- Integration and UI-Testing
- UI-Automation Testing Framework
- TestStack.White Overview
- Conclusion
- Outline
- Application Overview
- Writing Acceptance Tests
- Building a Bridge to User Interface Applying the Page Object Design Pattern
- Implementing Acceptance Tests
- Implementing ViewModel using TDD. Part 1.
- Implementing ViewModel using TDD. Part 2.
- Conclusion
- Outline
- What is TDD in the End?
- Agile and TDD
- TDD and Design Upfront
- Do Unit Tests Guarantee the Success?
- Having no Tests is Better than Having Bad Tests
- Architecture and Design
- Conclusion
- Outline
- Ending the TDD Day
- Pair-Programming & Ping-Pong Programming
- Quality of Tests
- Test Data
- Shouldly
- Prefer Positive if-Statements
- Testing Trivial Code
- Test Single Concern
- Singletons and Static Classes
- Builder Design Pattern. Immutability and Testability
- Conclusion