Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter also writes courses and teaches for Learning Tree International.
If you’re tired of reading articles about how to apply unit testing to new applications when most of your life is extending and enhancing legacy code, here’s a plan for (finally) exploiting automated testing when working with existing applications. It’s easier than you think, especially if you let Visual Studio and JustMock do the heavy lifting.
If you get your testers involved early enough, they can be the primary tool for ensuring that your users get what they want. In fact, testers can be the part of your process that users regard as “value added.”
If you want to create a great test plan for any application, there are four truths that will guide every decision you make. In fact, you’re already using them on a daily basis even if you’re not completely aware of it.
You should spend all the time on creating mock objects that you have to … and no more. Here are the three principles that will help you decide how much you actually need to do.