search

samuelcheongws / pe

0 stars 0 forks source link

Difficulty in testing import command #5

Open samuelcheongws opened 2 years ago

samuelcheongws commented 2 years ago

Coupled with the lack of manual testing documentation for the import command. Difficulty in testing a feature is considered a bug. No preset files are supplied for the application which makes testing within time constraints difficult.

  1. Documentation on how to use the feature is lacking
  2. No easy way to test the features with preset csv and json files
  3. Some error messages due to lack of personal data for each user is pointed out. As can be seen below: "name" : "Alex Yefffoh", "phone" : "87438807", "email" : "alexyeoh@example.com", this person is lacking some required inputs, however the file import system did not inform the user about this problem

While this feature as a standalone will not prevent the user from still using the application normally, the amount of issues caused by this bug makes it almost worth a high severity.

image.png image.png

nus-se-script commented 1 year ago

Team's Response

This bug report seems to contain multiple bugs, so I will address them and pick one.

  1. Documentation on how to use the feature is lacking: Not specified how the documentation is lacking. Hence this bug is unclear.

  2. No easy way to test the features with preset csv and json files: This is a valid bug.

  3. Some error messages due to lack of personal data for each user is pointed out: Per screenshot 2 (not sure what screenshot 1 means) it appears that single quotes (') have been used in place of double quotes (") in the JSON file, so the application is warning the user about that instead. Hence this bug is invalid.

Therefore I am picking bug 2. Bug 2 is valid, but I argue that it is not difficult to obtain CSV and JSON files for testing. For CSV files, you can use the export command to obtain a CSV file that can be modified for testing. For JSON files, you can create a copy of addressbook.json and modify it for testing.

The severity should be low as this bug does not affect usage of the application.

Items for the Tester to Verify

:question: Issue severity

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

Reason for disagreement: 1. Accepted

  1. Difficulty in testing is considered a medium bug.

Furthermore

  1. I did not add a single quote in the file. I duplicated the original addressbook file and deleted off key information about the user. The error is due to an incorrect error message. This would be considered a functionality bug.