Autoplay
Autocomplete
Previous Lesson
Complete and Continue
Learn Unit Testing with NUnit and C#
Getting Started
Download Source Code
01-Outline
02-What is a Unit Test
03-Unit Testing Frameworks
04-Your First Unit Test
05-Naming Conventions
06-Running and Debugging Unit Tests
07-Benefits of Unit Tests
08-Who Should Write Unit Tests and When
09-Programmer's Oath
10-DegreeConverter-Exercise
11-DegreeConverter-Solution
12-Conclusion
NUnit Testing Framework
01-Outline
02-Assert Intro
03-Assert Demo
04-Arrange-Act-Assert
05-Running Tests from the Console
06-SetUp and TearDown
07-OneTimeSetUp and OneTimeTearDown
08-Parameterized Unit Tests
09-Grouping and Ignoring Unit Tests
10-Code Coverage
11-FizzBuzz Exercise
12-FizzBuzz Solution
13-Roman Numerals Exercise
14-Roman Numerals Solution
15-Stack Exercise
16-Stack Solution
17-Conclusion
Test Doubles
01-Outline
02-Demo of a Testing Problem
03-Refactoring to Make Code Testable
04-Test Doubles
05-Hand-Rolled or Manual Test Doubles
07-Problems with Manual Test Doubles
08-Mocking Frameworks
09-Writing Unit Tests with a Mocking Framework
10-NSubstitute Mocking Framework. Key Features. Demo
11-Detroit School vs London School of Unit Testing
12-Conclusion
Intro to Test-Driven Development (TDD)
01-Outline
02-What is TDD
03-Red Green Refactor
04-TDD and Design Upfront
05-TDD-Demo
06-Conclusion
Unit Testing Best Practice
01-Outline
02-Do Unit Tests Guarantee the Success
03-Pragmatic Unit Testing
04-Integration Tests
05-Singletons and Static Classes
06-Header Interfaces
07-Demo of Refactoring to a Testable Design
08-How Much Test Coverage is Enough
09-Testing Trivial Code
10-The Rule of Testing a Single Concern
11-More on Best Practices
12-Generating Unit Test Method Signatures
13-Conclusion
08-Who Should Write Unit Tests and When
Lesson content locked
If you're already enrolled,
you'll need to login
.
Enroll in Course to Unlock