Hard to test feature.

[hernpiblo]

This part could have been text where the user can copy and paste into their own csv file to test out the import.
Now users have to manually type out everything just to test.
And the export function does not help since it does not export the same details as the required one for import.

[nus-pe-bot]

Team's Response

The purpose of our UG is to assist a user in using our application, not so that they can test whether our import feature works. In this case, a screenshot is sufficient in teaching the user how to use our import feature. As for the export feature, it is clearly stated in our UG that it serves a completely different purpose of helping hall admins send mass emails more easily. The purpose of export is not to export all of the residents' details, and it is not supposed to complement our import feature.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: The screenshot teaches the user how to use but it is difficult to test/try out the feature since you made the code block into a screenshot when it would benefit both you (in terms of maintaining text vs image) and the reader (in terms of being able to just copy the csv data into a temporary file to test this feature out).

This is not made any better by their inconsistent format between the UG and the screenshot as mentioned in another issue (#15).

I was unable to test this feature since there was just too much typing to be done just to test this function.

This will cause alot of inconvenience to users, since it is a crucial function, especially for your target audience who has to migrate from their old system and has to import their old data here

---

❓ Issue severity

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

• I disagree

Reason for disagreement: It is not a cosmetic issue. It can really cause severe inconvenience.

---