1. Introduction

This test plan outlines the test cases for the MoralDayX class (where X is One, Two, Three, and Four). These classes is responsible for displaying the screen where the player is to make their moral decision that will impact future levels.

2. Test Objectives

• Verify the correct initialisation of the MoralDayX class

3. Test Cases

3.1 Valid Initialisation

3.1.1 Valid Initialisation

• Test Method: testToggleVisibility_Hide()
• Objective: Verify that the MoralDayX class does not initialise when a game is started.
• Expected Result: The component should not initialise.

4. Test Execution

All tests should be executed as part of the test suite in InventoryComponentTest.java. The testing framework (JUnit) will report on the success or failure of each test case.

In addition to the automated tests, screen recordings will also be employed for testing purposes - these recordings will capture the gameplay experience and interactions with the MoralDayX class. This approach not only enhances the understanding of how the class performs under various scenarios but also aids in identifying any unexpected behaviour that may not be easily caught through traditional testing methods.

MoralDayOne -> money laundering night

https://github.com/user-attachments/assets/14b4e68d-3a62-4c8c-90c3-ffdc830f0a70

MoralDayTwo -> gambling night

https://github.com/user-attachments/assets/2244f600-4937-4d06-b3f3-6759905c1e35

MoralDayThree -> killing the health inspector

https://github.com/user-attachments/assets/ff3c9aa3-1584-4e33-b5d4-69d9da945fe3

MoralDayFour -> taking drugs with Rhino Boss

https://github.com/user-attachments/assets/920ebc31-b8a4-4378-8b97-e8084672715b

5. Conclusion

This test plan covers the functionality of the MoralDayX class, including initialisation. Successful execution of test cases will provide confidence in the robustness and correctness of the MoralDayX implementation.