tailieunhanh - Growing Object-Oriented Software, Guided by Tests- P2

Growing Object-Oriented Software, Guided by Tests- P2: Test-Driven Development (TDD) hiện nay là một kỹ thuật được thành lập để cung cấp các phần mềm tốt hơn nhanh hơn. TDD là dựa trên một ý tưởng đơn giản: các bài kiểm tra Viết cho code của bạn trước khi bạn viết đoạn code riêng của mình. Tuy nhiên, điều này "đơn giản" ý tưởng có kỹ năng và bản án để làm tốt. Bây giờ có một tài liệu hướng dẫn thiết thực để TDD mà sẽ đưa bạn vượt ra ngoài những khái niệm cơ bản. Vẽ trên một. | Chapter 3 An Introduction to the Tools @RunWith O public class AuctionMessageTranslatorTest private final Mockery context new JUnit4Mockery @ private final AuctionEventListener listener private final AuctionMessageTranslator translator new AuctionMessageTranslator listener @Test public void notifiesAuctionClosedWhenCloseMessageReceived Message message new Message SOLVersion Event CLOSE new Expectations oneOf listener .auctionClosed UNUSED_CHAT message o The @RunWith annotation tells JUnit to use the jMock test runner which automatically calls the mockery at the end of the test to check that all mock objects have been invoked as expected. The test creates the Mockery. Since this is a JUnit 4 test it creates a JUnit4Mockery which throws the right type of exception to report test failures to JUnit 4. By convention jMock tests hold the mockery in a field named context because it represents the context of the object under test. The test uses the mockery to create a mock AuctionEventListener that will stand in for a real listener implementation during this test. The test instantiates the object under test an AuctionMessageTranslator passing the mock listener to its constructor. The AuctionMessageTranslator does not distinguish between a real and a mock listener It communicates through the AuctionEventListener interface and does not care how that interface is implemented. The test sets up further objects that will be used in the test. The test then tells the mockery how the translator should invoke its neighbors during the test by defining a block of expectations. The Java syntax we use to do this is obscure so if you can bear with us for now we explain it in more detail in Appendix A. This is the significant line in the test its one expectation. It says that during the action we expect the listener s auctionClosed method to be called exactly .