Creating Ordered Tests
by Mike Snell, Lars Powers
Microsoft Visual Studio 2015 Unleashed, Third Edition
- About This eBook
- Title Page
- Copyright Page
- Contents at a Glance
- Table of Contents
- About the Authors
- Dedication
- Acknowledgments
- We Want to Hear from You!
- Reader Services
- Introduction
- Part I: Introducing Visual Studio 2015
- Chapter 1. A Quick Tour of Visual Studio 2015
- Chapter 2. The Visual Studio IDE
- Chapter 3. The .NET Languages
- What’s New in C# 6.0 and VB 14
- Language Primer
- Language Features
- Infer a Variable’s Data Type Based on Assignment
- Create an Object and Initialize Its Values (Object Initializers)
- Define a Collection and Initialize Its Values
- Creating an Instance of a Nonexistent Class
- Add Methods to Existing Classes (Extension Methods)
- Add Business Logic to Generated Code (Partial Methods)
- Access and Query Data Using the .NET Languages
- Write Simple Unnamed Functions Within Your Code (Lambda Expressions)
- Splitting an Assembly Across Multiple Files
- Working with XML Directly Within Your Code (VB Only)
- Removing Unused Arguments from Event Handlers (VB Only)
- Creating an Automatically Implemented Property
- Dropping the Underscore in VB for Line Continuation
- Working with Dynamic Languages/Objects
- Covariance and Contravariance
- Asynchronous Programming
- The .NET Framework
- Summary
- Part II: An In-Depth Look at the IDE
- Chapter 4. Solutions and Projects
- Chapter 5. Browsers and Explorers
- Chapter 6. Introducing the Editors and Designers
- Part III: Working with the Visual Studio Tools
- Chapter 7. Working with Visual Studio’s Productivity Aids
- Chapter 8. Testing Code
- Chapter 9. Refactoring Code
- Chapter 10. Debugging Code
- Chapter 11. Deploying Code
- Chapter 12. Developing Applications in the Cloud with Windows Azure
- Chapter 13. Working with Databases
- Part IV: Extending Visual Studio
- Part V: Building Web Applications
- Chapter 17. Building Modern Websites with ASP.NET 5
- Chapter 18. Using JavaScript and Client-Side Frameworks
- Chapter 19. Building and Consuming Services with Web API and WCF
- Part VI: Building Windows Client Apps
- Chapter 20. Building Windows Forms Applications
- Chapter 21. Building WPF Applications
- Chapter 22. Developing Office Business Applications
- Part VII: Creating Mobile Apps
- Chapter 23. Developing Windows Store Applications
- Chapter 24. Creating Windows Phone Applications
- Chapter 25. Writing Cross-Platform Mobile Applications with Apache Cordova
- Index
- Code Snippets
Creating Ordered Tests
Visual Studio enables you to group unit tests, set their sequence of execution, and treat the results as if a single test was run. This can be useful if you need to write unit tests that are dependent on one another. For example, you might insert a record in one test and rely on that record being there in a later test. Of course, this goes against a good practice for unit testing; each test should be able to execute independently. Thankfully, you can create an ordered test that groups the individual unit tests into a new, self-contained test.
You add an ordered test to your test project by right-clicking the unit test project and selecting Add, Ordered Test. You can also select the Ordered Test template from the Add New Test dialog box.
An ordered test is simply an XML file based on the OrderedTest schema. You do not, however, need to hand-edit the XML. Instead, Visual Studio gives you the ordered test designer to help you. Figure 8.15 shows an example of this designer.
FIGURE 8.15 You add existing unit tests to an ordered test to create a new test that executes two or more tests in a specific order.
The left side of the dialog box is where you find all your tests in your solution. Tests are shown by test name. You select individual tests from the left side and use the arrow (>) in the middle to include the tests in your ordered test. You can use the up and down arrows on the right side to change the order in which your tests execute.
The ordered test becomes its own test within your test project. You can then run it by itself or as part of a larger group. When run, Visual Studio executes each unit test in the order you defined. If any fail, the entire ordered test fails unless you have checked the Continue After Failure check box (located on the bottom of the dialog in Figure 8.15). You can view the details of the failed ordered test to see which tests passed and which failed. Figure 8.16 shows the ordered test inside the Test Explorer being run. Notice the first item (compute for negative) failed, so the other two tests in the ordered test were not run.
-
No Comment