One of the biggest challenges in writing test automation scripts comes in keeping pace with the rapid changes of the application under test. One small “critical” change made by a dev at midnight can result in hours of painful investigation and test script repair for you the next morning(s).
When you need to perform unit testing in an independent way, you use mock objects. Mock objects are simulated objects that mimic the behavior of real objects in controlled ways. In this excerpt of their book “Pragmatic Unit Testing in C# with NUnit”, Andy Hunt, Dave Thomas and Matt Hargett explain how to avoid coupling when you build your C# unit tests.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates