Enterprise Java Development@TOPIC@

Chapter 24. Project 2 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 tests that verify the EJB functionality of eSales accessed through its remote interface. This will also test the DTOs. These tests should be packaged in the eSales RMI Test project.

  2. Provide JUnit tests that verify the extra business logic functionality of eBidbot interfacing with eSales. These tests may be placed either with the business logic project or where you test the remote interfaces.

  3. Provide JUnit tests that verify the EJB functionality of eBidbot accessed through its remote interface. This will also test its use of DTOs. Theses tests should be packaged in the eBidbot WAR (or optional RMI Test) project.

  4. Perform an end-to-end use case to do the following. This must be demonstrated in an automated JUnit test and then be manually implementable using the Web UI.

    1. Reset all eSales and eBidbot tables (using the SalesTestUtilEJB and BidbotTestUtilEJB)

    2. Populate the eSales tables (using the Ingestor)

    3. Create account for seller, buyer1, and buyer2 in eSales

    4. Create account for buyer2 in eBidbot

    5. Create auction for seller

    6. Get auctions for seller

    7. Get auction for the one created in earlier step

    8. Get open auctions

    9. Place bid for buyer1

    10. Get auctions for buyer1

    11. Place order for buyer2 in eBidbot (stimulate a bid)

    12. Get auction to verify bids were placed for buyer1 and buyer2