Đang chuẩn bị liên kết để tải về tài liệu:
Java Extreme Programming Cookbook phần 8

Các đầu ra ví dụ cho thấy một bài kiểm tra thời gian mà không ngay lập tức và khác mà chờ đợi cho đến khi phương pháp được thử nghiệm hoàn tất. Các kết quả cơ bản được kiểm tra cùng cả hai không nhưng thông điệp in là khác nhau. | at com.clarkware.junitperf.TimedTest.runUntilTestCompletion Unkno wn Source at com.clarkware.junitperf.TimedTest.run Unknown Source at com.oreilly.javaxp.junitperf.TestPerfSearchModel.main TestPerf SearchModel. java 48 FAILURES Tests run 2 Failures 2 Errors 0 The example output shows a timed test that fails immediately and another that waits until the method under test completes. The underlying results are the same both tests fail but the printed message is different. A nonwaiting test or a test that fails immediately is unable to print the actual time it took to complete the test. Maximum elapsed time 1000 ms exceeded On the other hand a test that fails after the method under test completes provides a better message. This message shows the expected time and the actual time. Maximum elapsed time exceeded Expected 1000ms but was 1002ms. As you can see from the previous output this test is really close to passing. An important point to make here is that when a test is repeatedly close to passing you may wish to increase the maximum allowed time by a few milliseconds. Of course it is important to understand that performance will vary from computer to computer and JVM to JVM. Adjusting the threshold to avoid spurious failure might break the test on another computer. If you need to view some basic metrics about why a timed test failed the obvious choice is to construct a timed test that waits for the completion of the method under test. This helps to determine how close or how far away you are from having the test pass. If you are more concerned about the tests executing quickly construct a timed test that fails immediately. Example 8-1 shows a complete JUnitPerf timed test. Notice the use of the public static Test suite method. This is a typical idiom used when writing JUnit tests and proves invaluable when integrating JUnitPerf tests into an Ant buildfile. We delve into Ant integration in Recipe 8.7. Example 8-1. JUnitPerf TimedTest package .