Automation is key for an effective testing process. Every test case we devise here is later automated via a testing framework such as JUnit. Let me clearly distinguish between test case design and test case execution. Once a test case is written, a framework runs it and shows reports, failures, and so on. This is all that these frameworks do. Their role is very important, but the real challenge in software testing is not writing JUnit code but designing decent test cases that may reveal bugs. Designing test cases is mostly a human activity.
NOTE If you are not familiar with JUnit, it should not be a problem, because the examples in the are easy to read. But as I mention throughout the more familiar you are with the testing framework, the better.
I discuss testing techniques, we first engineer the test cases and only later automate them with JUnit code. In real life, you may mingle both activities; but I decided to keep them separate so you can see the difference. This also means the does not talk much about tooling. JUnit and other testing frameworks are powerful tools, and I recommend reading the manuals.
Leave a Reply