To start off, can you go through the application, use all the features and make sure they work?
Eg make sure that:
Stored files are updated properly when changes are made, and that the user can see the changes being reflected when they select options to print entities. Eg after deleting a camp, the camps.json should be updated, and the camp should no longer be listed when the user prints all camps.
No infinite loops/ getting stuck
Provide erroneous input (eg type in non-digit values and negative values for resource amounts) and see if the application catches that and relays useful feedback to the user
No weird application behavior
Try to use the weirdest edge cases for testing and see if the application breaks
For example, see if the app works in the following scenarios:
There is only 1 admin, and no other users
There is only 1 volunteer, and no other users
There is a plan, but with no camps, no refugees, no resources
There is a camp inside a plan, but with no refugees and no resources
All plans, camps, resources, refugees deleted
(To create these scenarios, you might want to delete entities directly from the json files, or alternatively use delete entity options that we've built in the app. Whichever is more convenient for you is fine.)
Think about how Ghita would try and break our code! Maybe keep a pen and paper next to you so you can keep track of the changes.
To start off, can you go through the application, use all the features and make sure they work? Eg make sure that:
Try to use the weirdest edge cases for testing and see if the application breaks For example, see if the app works in the following scenarios:
Think about how Ghita would try and break our code! Maybe keep a pen and paper next to you so you can keep track of the changes.