Lack of seeded data

[jiachen247]

Lack of seed data in the app which makes it hard for testing

[nus-pe-bot]

Team's Response

When we uploaded the JAR file, we intended it to be for users who may be starting from a blank state. We would have no idea what kind of data the user would be adding into the application. As such, we only did minimal seeding (only 2 blank resumes) for the application.

We do agree that it may have been easier to test had there been seeded data, but we also felt that if we seeded it too much, some testers might be confused when trying our commands such as add, because they might not be sure whether the new items have been added properly or not. This is as opposed to starting from a clean state, and testers can be sure that they have added new items to the application.

Due to the reasons above, we would have mark it as NotInScope. We will also mark it as VeryLow severity, because taking the perspective of the user starting from a clean state, the lack of data would not affect their user experience.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: From my discussions with my TA kush, we were expected to provide seeded data to make testing easier!

---

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---