Good developers know that name choice is important when building classes and methods. Following a logical and coherent naming convention is important for test methods too. This video looks at several popular unit test naming patterns that strive to make test names self-documenting.
- [Voiceover] Good developers know that name choice…is important when making classes and methods.…Following a logical and coherent naming convention…is important for test methods too.…In this video, I'll look at several…popular naming patterns that strive…to make test names self documenting.…This first example shows a common…pattern for naming test classes.…That's where the name of the class is identical…to the name of the system under test class.…The only difference is using the…suffix test at the end of this class.…
The idea is that all the tests for the system under…test class are contained within this test class.…Over at my brokerage light project…I have a payment date class, shown on line five,…and my test project I have on line three,…the PaymentDateTests.…I also have a commission calculator class…in my brokerage light, so I should also have…a matching commission calculator test class.…And I do.…As far as naming methods, this is using a very old school…way of doing it, where I use the name of the method…that I'm testing and then the word test at the end.…
Author
Walt Ritscher
Released
6/16/2016- Examining types of frameworks
- Choosing a naming convention
- Creating unit tests
- Running unit tests with Visual Studio
- Modifying and correcting code
- Handling exceptions
- Installing and using nUnit
- Viewing test results with CodeLens
Skill Level Intermediate
Duration
Views
Q: This course was updated on 08/22/2017. What changed?
A: New videos were added that cover live unit testing and creating a project with the unit test framework.
-
Introduction
-
Welcome1m
-
-
1. Create a Simple Unit Test Framework
-
What are unit tests?6m 23s
-
Add the test projects1m 14s
-
Analyze which tests to run2m 10s
-
Create a simple test4m 45s
-
Create a simple test runner3m 46s
-
Add additional tests2m 59s
-
Refactor the test runner3m 59s
-
Create an Assert class5m 20s
-
Use the Assert class3m 49s
-
-
2. Unit Testing Conventions
-
Choose a naming convention5m 59s
-
-
3. Work with Visual Studio Unit Testing Framework
-
Create the unit test4m 16s
-
Run the unit test3m 21s
-
Modify code to pass test4m 53s
-
Expected exceptions4m 27s
-
Test parameters4m 9s
-
4. Work with xUnit
-
Install xUnit2m 21s
-
Expected exceptions4m 55s
-
Test multiple parameters2m 13s
-
-
5. Work with nUnit
-
Install nUnit2m 9s
-
Create and run a unit test2m 25s
-
Use the nUnit constraints3m 44s
-
More nUnit constraints6m 16s
-
Test parameters2m 21s
-
-
6. Additional Topics
-
Get more from your tests4m 40s
-
Debug unit tests2m 8s
-
Use the test menus3m 27s
-
Conclusion
-
Next steps1m 1s
-
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Choose a naming convention