- Software Testing using Visual Studio 2010
- Table of Contents
- Copyright
- Credits
- About the Authors
- About the Reviewers
- Preface
- 1. Visual Studio 2010 Test Types
- 2. Test Plan, Test Suite, and Manual Testing
- 3. Automated Tests
- 4. Unit Testing
- Creating unit tests
- Assert statements
- Types of asserts
- Assert
- StringAsserts
- CollectionAssert
- CollectionAssert.AllItemsAreNotNull
- CollectionAssert.AreEquivalent
- CollectionAssert.AreNotEquivalent
- CollectionAssert.AllItemsAreInstancesOfType
- CollectionAssert.IsSubsetOf
- CollectionAssert.IsNotSubsetOf
- CollectionAssert.AllItemsAreUnique
- CollectionAssert.Contains
- CollectionAssert.DoesNotContain
- CollectionAssert.AreEqual
- CollectionAssert.AreNotEqual
- AssertFailedException
- UnitTestAssertionException
- ExpectedExceptionAttribute
- Types of asserts
- Unit tests and generics
- Data-driven unit testing
- Unit testing an ASP.NET application
- Unit testing web services
- Code coverage unit test
- Summary
- 5. Web Performance Testing
- 6. Advanced Web Testing
- 7. Load Testing
- 8. Ordered and Generic Tests
- 9. Managing and Configuring a Test
- 10. Command Line
- 11. Working with Test Results
- 12. Reporting
- 13. Test and Lab Center
- Index
Before publishing the test result we have to store the test results in a trace file. Use the /tracefile option with the MSTest command line to store the test results. The default extension for the trace file is .trx. It is better to use the same extension when we force Visual Studio to use a specific trace file for the test results.
For example:
MSTest /testmetadata:TestProject.vsmdi /testfile:TestProject.trx
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.