Enterprise Java Development@TOPIC@

Chapter 19. Project 1 Testing

Note

The end-to-end scenario will test your business logic, DAO, and BOs 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 tests.

  1. Provide a JUnit test for your business objects (BOs) that test the manipulation of data. An example test might be to try forming a contest between teams in separate divisions or schedule a contest that conflicts with a team and/or venue schedule. These tests should be packaged with the BOs. There should be a separate project and test for both eLeague and eClub. It is anticipated that these tests will be a minimal demonstration of understanding.

  2. Provide a JUnit test for your eLeague and eClub JPA DAOs. This should test the implementation for the required CRUD operations for each type of object. It is understood that some of the operations will be handled by cascades, so you might not have a set of methods handling each type of business object. This test should be packaged with the DAOs.

  3. Provide a JUnit test for your business logic to test the basic functionality of your business logic design, including ingest. The ingestor test should be able to reference a known data file and ingest records into the database using the DAOs. These tests should be packaged with the business logic implementation.

  4. Provide a set of JUnit test programs to verify the following end-to-end scenario in eLeague. This test should be implemented as a JUnit test and packaged with the business logic implementation.

    1. reset (using LeagueTestUtil) -- reset the eLeague database to an initial starting state.

    2. ingest data (using LeagueIngestor) -- ingest the full XML test data file.

    3. createClub (using LeagueMgmtImpl)

    4. addVenue (using ClubMgmtImpl)

    5. addTeam (using ClubMgmtImpl)

    6. updateContact for team (using ClubMgmtImpl)

    7. assignTeamDivision (using LeagueMgmtImpl) - divisions already exist for current/next season within the test data.

    8. scheduleSeason (using ContestMgmtImpl)

    9. getDivisions (using LeagueMgmtImpl)

    10. getDivisionStandings (using LeagueMgmtImpl)

    11. getTeam with schedule and results (using LeagueMgmtImpl)

    12. reportScore (using ContestMgmtImpl)

    13. getTeam with schedule and results (using LeagueMgmtImpl)

    14. getDivisionStandings (using LeagueMgmtImpl)

  5. Provide a set of JUnit test programs to verify the following end-to-end scenario in eClub. This test should be implemented as a JUnit test and packaged with the business logic implementation. Note that it is anticipated that you may only have time to create one team, with one player, manager, parent, and coach for the club.

    1. reset (using OrganizationTestUtil) -- reset the organization database to an initial starting state.

    2. createParent (MemberMgmtImpl) - parent depicted as Individual

    3. createPlayer (MemberMgmtImpl)

    4. createCoach (MemberMgmtImpl)

    5. createTeam (using OrgMgmtImpl)

    6. assignPlayers (using OrgMgmtImpl)

    7. assignCoach (using OrgMgmtImpl)

    8. assignManager (using OrgMgmtImpl)

    9. getTeamRoster (using OrgMgmtImpl)

    10. getTeamSchedule (using OrgMgmtImpl) - this will later call eLeague for Contest information, but for now simply returns an empty list.