The Visual Studio Test Explorer is well adapted to working with third party testing frameworks. But it has a definite way of displaying the test methods in the UI. xUnit has a set of configuration settings that change the way the tests are displayed in Test Explorer. This tutorial looks at how to use the app.config XML file to change the xUnit test name to a more readable format.
- [Voiceover] I've talked about naming conventions…elsewhere in this course.…I suggested that you should use a descriptive name…for your class.…In my case, I'm using a scenario name,…Getting a Payment Should.…And I've also suggested using a long name…for the test method.…In this case it's what should happen.…Returns date 30 days in the future…when proposed date falls on a weekday.…This works great for describing it,…but if you look in the Test Explorer,…you'll see that it truncates the end of the method name.…In Test Explorer, you can Group by Class.…
Now I can see the methods for GettingAPaymentDate_Should…listed here.…Unfortunately, they still show the fully qualified name,…so it's BrokerageLib.xUnit.GettingAPayment_Should and so on.…It's possible to add an app config file to my xUnit Project…and tell Text Explorer that I only wanna see…the method name.…Here's how you do that.…The file will be called App.config.…
And here I need to use an xUnit-specific syntax.…So I'm setting the method display to show in Test Explorer.…
Author
Walt Ritscher
Updated
8/29/2017Released
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
-
Welcome59s
-
-
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
-
Live unit testing4m 56s
-
Conclusion
-
Goodbye1m 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: Use App.config to shorten names in Test Explorer