Test Specification: Stuff Lending System

This is an informal specification of tests to perform when you are done with the assignment design and implementation. It is adviced to perform all tests before the final release. If you find problems you fixt them and again perform all tests.

The test cases are written in a general form and you may need to adapt them to your specific implementation and the decisions you have made during the implementation. In that case submit a refined test spec as a project deliverable.

General

1. Clone the application from gitlab into a new directory. Avoid running the application in the development environment.
2. run the application with ./gradlew run -q --console=plain
3. If you cannot perform one of the steps in the application e.g. it crashes or does not behave as stated you have found a bug. Document it and run the rest of the test cases.

Test Report

The test repors is a simple list of test cases performed and the result, i.e. working or not working. If it is not working note what step and what the result was.

You should have a final test report in your repository when handing in the assignment.

Example Test Report

Version #234234 (git commit hash/link)
Date: 2022.08.17
Environment: Windows, Java version 18. Performed by: Tobias

Test Cases

5.1 Member Data

Requirement: 5

1. Check that there are at least 3 Members.
2. Check that one member (M1) with 500 credits. M1 has two items for lending, I1 with cost 50 one cheap I2 cost 10
3. Check that one member (M2) with 100 credits. M2 has no items for lending.
4. Check that one member (M3) with 100 credits has an active lending contract for I2 that starts on day 5 and ends on day 7 (3 days).

1.1 Create Member

Requirement: 1.1, 1.1.1, 1.4

1. Create a member with name: "Allan Turing", email: "allan@enigma.com", phone: "123456"
2. Check that the member is created correctly with an id according to the requirement by checking the members full information.
3. Quit the application

1.2 Create Member - Duplicate Email and Phone

Requirement: 1.1, 1.1.1, 1.1.2, 1.4

1. Create a member with name: "Allan", email: "allan@enigma.com", phone: "123456"
2. Check that the member is created correctly with an id according to the requirement by checking the members full information.
3. Create a member with name: "Turing", email: "allan@enigma.com", phone: "123"
4. Check that the member is not created (duplicate email)
5. Create a membner with name: "Turing", email: "turing@enigma.com", phone: "123456"
6. Check that the member is not created (duplicate phone)
7. Create a member with name "Turing" , email: "turing@enigma.com", phone: "123"
8. Check that the member is created correctly with an id according to the requirement by checking the members full information.
9. Quit the application

1.3 Delete Member

Requirement: 1.1, 1.1.1, 1.1.2, 1.4

1. Create a member with name: "Allan", email: "allan@enigma.com", phone: "123456"
2. Check that the member is created correctly with an id according to the requirement by checking the members full information.
3. Delete the member
4. Check that the member is deleted by listing all members (simple)
5. Create a member with name: "Allan", email: "allan@enigma.com", phone: "123456"
6. Check that the member is created correctly with an id according to the requirement by checking the members full information.
7. Quit the application.

2.1 Create item

1. Create an item for a Member
2. Check that the item is created and part of the Members items by inspecint the member's details.
3. Check that the owner member has increased it's credits with 100

2.2 Delete item

1. Select a member with one or several items
2. Delete one of the member's items that is not involved in any contract
3. Check that the item was deleted from the members owned items

2.3 Delete item

1. Select a member with one or several items
2. Delete one of the member's items that is booked (i.e. a future contract)
3. Check that the item was deleted from the members owned items
4. Check that the contract was cancelled

3.1 Create Contract

1. Create a contract for I2 lending to M2, 3 days of lending, day 1 to and including day 3
2. Check that the contract was created

3.2 Create Contract - not enough funds

1. Create a contract for I1 lending to M2, 3 days of lending (e.g. day 1 to and including day 3)
2. Check that the contract was not created due to lack of funds

3.3 Create Contract - conflicting time

1. Create a contract for I2 lending to M2, 3 days of lending, day 4 to and including day 6
2. Check that the contract was not created due to conflicting time

3.4 Create Contract - conflicting time

1. Create a contract for I2 lending to M2, 3 days of lending, day 6 to and including day 9
2. Check that the contract was not created due to conflicting time

3.5 Create Contract - conflicting time

1. Create a contract for I2 lending to M2, 3 days of lending, day 4 to and including day 9
2. Check that the contract was not created due to conflicting time

3.6 Create Contract - conflicting time

1. Create a contract for I2 lending to M2, 3 days of lending, day 6 to and including day 6
2. Check that the contract was not created due to conflicting time

4.1 Advance time

1. Advance the time 8 days.
2. Check that the contract has been fullfilled and that funds have been deduced from M3 who now has 70 credits.