Enterprise Java Development@TOPIC@

Chapter 24. Project 2 Testing

Tip

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 test cases.

  1. Provide a JUnit integration test that verifies the eLeagueEAR can be deployed to the server, including successful deployment of the persistence unit and contained EJBs.

  2. Provide a JUnit unit test that verifies successul marshaling and demarshaling of an eLeague DTO class using Java Serialization. You may create a DTO class specifically for this test if none of your DTOs are used in your RMI interface.

  3. Provide a JUnit integration test that verifies a successful JNDI lookup and RMI communication with an eLeagueEJB.

  4. Provide a JUnit unit test that verifies successul marshaling and demarshaling of an eLeague DTO class to/from XML or JSON.

  5. Provide a JUnit integration test that verifies a successful HTTP communication with an eLeagueEJB.

  6. Create a single JUnit integration test case (e.g., eSportEndToEndIT) with a single @Test method that walks the two applications through the following end-to-end scenario. You may create a separate IT test in eLeague while developing the eLeague portions but the final end-to-end scenario should be placed in eClub since eClub depends on eLeague.

    1. Deploy the applications

    2. Reset all eLeague tables (using the LeagueTestUtilEJB)

    3. Populate the eLeague tables (using LeagueTestUtilEJB and the LeagueIngestor)

    4. Reset all eClub tables (using the ClubTestUtilEJB)

    5. Populate the eClub tables (using ClubTestUtilEJB) *if* anything necessary

    6. Create a Club in eLeague (using the LeagueMgmtEJB). Assign the club representative to have the login of "user2"

    7. Add Venue for Club in eLeague (using ClubMgmtEJB)

    8. Create Parent in eClub (using MemberMgmtEJB). Assign this user login of "user3".

    9. Create Player in eClub (using MemberMgmtEJB)

    10. Add a Coach role in eClub (using MemberMgmtEJB)

    11. Create a Team in eClub (using OrgMgmtEJB)

    12. Assign Players to a Team in eClub (using OrgMgmtEJB)

    13. Assign Coach to a Team in eClub (using OrgMgmtEJB)

    14. Assign Manager to a Team in eClub (using OrgMgmtEJB)

    15. Show team roster in eClub (using OrgMgmtEJB)

    16. Add a Team for Club in eLeague (using ClubMgmtEJB)

    17. Add a contact for a Team eLeague (using ClubMgmtEJB)

    18. Assign a Team to an existing Division eLeague (using ClubMgmtEJB; division=U13-A, refid="Division-845")

    19. Schedule a Season eLeague (using ContestMgmtEJB)

    20. Project 3 placeholder

    21. Project 3 placeholder

    22. Show a Team Schedule in eClub (using OrgMgmtEJB)

    23. Project 3 placeholder

    24. Project 3 placeholder

    25. Report a Score in eLeague (using ContestMgmtEJB)

    26. Show Division Standings in eLeague (using LeagueMgmtEJB)

    Sport End to End Scenario is demonstrated using single IT @Test

    To be clear. The above scenario should be both automated with a single JUnit test. Any Web UI actions you implement can augment these actions but not replace them.