-
Notifications
You must be signed in to change notification settings - Fork 4
Deliverable 1 Testing Report
jdbc:postgresql://ec2-54-235-77-0.compute-1.amazonaws.com:5432/ddks65sh78n85l?user=mmjhhgytguljbz&password=4c3d5413d61e4fa69017f7665aee01094712d493aec673f9c53b8d1b6229f736&sslmode=require
Our goal is to perform Junit tests of the persistence layer. The persistence layer needs to be developed to try one read and one write operation for each class of the domain model, and it allows to remove all contents of the database.
- Create an employer
- Create a Coop Term
- Create an Event
Test 1 - Employer Test
Employer can create an account through the COOPERATOR system with valid email and password. Employer has three attributes: userEmail, userPassword, and companyName. In the persistence test, it is necessary to test all the possible cases when a user create an employer account. In this case, the following tests are performed:
- test CreateEmployer with valid attributesIt is also necessary to perform "read" and "clear" operation tests. Therefore, the following tests are performed:
- test CreateEmployer with null email
- test CreateEmployer with null user password
- test CreateEmployer with null company name
- test getEmployer with valid ID inputTest 2 - Coop Term Test
- remove all contents of database
A student might have more than one coop term throughout their school years, and each coop term class contains only information associated with one coop term. A Coop term contains the following attributes and objects: location, startDate (date of starting the coop term), ifWorkPermitNeeded, academic semester, job Description, employer, student, academic manager and endDate. The following read, write and clear tests are performed:
- test CreateCoopTerm with valid attributes
- test CreateCoopTerm with null location
- test CreateCoopTerm with invalid start date month
- test CreateCoopTerm with invalid start date year
- test CreateCoopTerm with null start date
- test CreateCoopTerm with null ifWorkPermitNeeded
- test CreateCoopTerm with null job Description
- test CreateCoopTerm with null academic semester
- test CreateCoopTerm with null employer
- test CreateCoopTerm with null student
- test CreateCoopTerm with null academic manager
- test CreateCoopTerm with null end date
- test CreateCoopTerm with invalid end date month
- test CreateCoopTerm with invalid end date year
- test getCoopTerm with valid ID input
- remove all contents of database
Test 3 - Event Test
Employers could be notified about or invited to upcoming events. Event has five attributes: start date, end date, location, start time and end time. The following read, write and clear operations are performed:
- test CreateEvent with valid attributes
- test CreateEvent with null start date
- test CreateEvent with null end date
- test CreateEvent with null location
- test CreateEvent with null start time
- test CreateEvent with null end time
- remove all contents of database
All the Junit tests are successful. The project could successfully compile, build and run the test suite of the persistence layer.
- Reports
- Minutes
- Effort Table
- Architecture Model
- Report
- Minutes
- Effort Table
- Reports
- Minutes
- Effort Table
-
Reports
-
Minutes
-
Effort Table