Enterprise Java Development@TOPIC@

Chapter 28. Project 3 Testing

Note

The end-to-end scenario will test your end-to-end application in a "happy path" scenario. Any white-box or black-box testing of alternate and error paths would be appropriate to put in the separate unit and IT tests.

  1. Provide JUnit IT tests that verify the EJB functionality of eSales accessed through its remote interface using new access control restrictions.

  2. Provide JUnit IT tests that verify the EJB functionality of eBidbot using its new access control restrictions and ability to authenticate with eSales.

  3. Provide a JUnit IT tests that demonstrates the functionality of the JavaEE interceptor/validator.

  4. Implement the scripted use case below as an automated JUnit test and manually accessed script through the Web UI. All command line implementations must be wrapped in an Ant runtime script to encapsulate the classpath details in a portable manner (see the class jmsNotifier project for an example of using an Ant runtime script). The full JSE subscriber need not be part of the automated end-to-end JUnit test. The JUnit test/module must be delivered in a state that can be executed in a debugger -- whether directly within Eclipse or using a remote debugging session.

    1. eSales initializes the EJB Timer to check for expired auctions

    2. eBidbot initializes the EJB Timer to check auctions associated with its bids.

    3. admin1 resets all eSales tables (using the eSalesTestUtilEJB)

    4. admin1 populates the eSales tables (using the ESalesIngestor)

    5. admin2 resets the eBidbot tables (using the EBidbotTestUtilEJB)

    6. admin2 populates the eBidbot tables (using the EBidTestUtilEJB) if necessary. Suggest adding account for user3 at this point.

    7. user1 creates auction

    8. user2 gets a list of open auctions

    9. user2 places bid on an auction

    10. user2 views the current status of the auction they are bidding on

    11. user3 gets a list of open auctions

    12. user3 views the current status of the auction that was bid by user2

    13. user3 places order with eBidbot

    14. eBidbot EJB wakes up from an EJB Timer

    15. eBidbot EJB places bid for user3

    16. user2 places another bid on auction

    17. eBidbot EJB wakes up again from an EJBTimer

    18. eBidbot EJB sees they have been raised and places another bid for user3

    19. eSales EJB wakes up from an EJBTimer and closes the auction

    20. eSales EJB publishes a message to the topic that informs everyone of the closing and that user3 has win.

    21. The eBidbot MDB receives the message and updates the order.

    22. The stand-alone client recieves the message if it matches their JMS selector for a specific category.

    23. user3 checks their order with eBidbot and finds out they won

Figure 28.1. eMarket Full Sequence

eMarket Full Sequence