B
backwards compatible base class implementation table of components batchtest Bean Scripting Framework, Ajax BeanUtils beginXXX best practices always specify a reason for skipping a test always verify that the test fails when it should fail assertions helper choose meaningful test method names continuous regression testing create complementary tests database testing database tests don’t hardcode values don’t write business locic in mock objects EasyMock object creation explain the failure reason in assert calls JSLint let the test improve the code, 2nd make exception tests easy to read make sure target database is tested one database per developer one unit test equals one @Test method plan your dataset usage refactor
Get JUnit in Action, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.