Unit Testing Benefits, Techniques & MSTest Introduction
•Download as PPTX, PDF•
2 likes•409 views
The document discusses unit testing, including definitions of units and unit testing. It describes the benefits of unit testing over traditional testing such as easier isolation of errors and catching problems earlier. Specific unit testing techniques are covered like test-driven development, isolation using stubs and mocks, and an introduction to the MSTest framework for writing unit tests. The document recommends applying unit testing to software development for benefits like faster debugging, reduced costs, and improved code design.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Unit Testing Benefits, Techniques & MSTest Introduction
Similar to Unit Testing Benefits, Techniques & MSTest Introduction (20)
Recently uploaded
Recently uploaded (20)
Unit Testing Benefits, Techniques & MSTest Introduction
- 1. Hatim Al Sum Software Development Specialist
- 2. Definition Unit Testing vs Traditional Testing Benefits of Unit Testing Test Driven Development Isolation Techniques Introduction to MSTest Where to Apply
- 3. Unit : ◦ The smallest piece of code software that can be tested in isolation. Unit Testing : ◦ A unit test is a piece of code (usually a method) that invokes another piece of code and checks the correctness of some assumptions afterward. If the assumptions turn out to be untrue, the unit test has failed.
- 4. Test the system as a whole Individual components rarely tested Errors go undetected Isolation of errors difficult to track down
- 5. Each part tested individually All components tested at least once Errors picked up earlier Scope is smaller, easier to fix errors
- 6. Isolatable Repeatable Automatable Easy to Write
- 7. Faster Debugging Faster Development Better Design (Redesign may be needed) Excellent Regression Tool Reduce Future Cost (Cost Effective)
- 8. Test before Coding Design Test-> Develop ->Test -> Re Develop.
- 9. Stubs : ◦ A stub is a controllable replacement for an existing dependency in the system. ◦ By using a stub, you can test your code with-out dealing with the dependency directly. ◦ Simulator of External Dependencies Mocks: ◦ A mock object is a fake object in the system that decides whether the unit test has passed or failed. It does so by verifying whether the object under test interacted as expected with the fake object. There’s usually no more than one mock per test
- 11. The class under test communicates with the mock object, The test uses the mock object to verify that the test passes.
- 12. Show Idea Test App Design Test Cases Retest Fix Errors Retest