soc-pe-bot
commented
19 hours ago [IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Team's Response
This is a valid issue, but the team believes it is of low severity because it has no impact on functionality or data integrity; the file is imported correctly regardless of case. This is a rare edge case, as most users do not have similarly named files differing only by case, especially on case-insensitive systems. Furthermore, the export command always exports data to a file named ExportedContacts.csv, overwriting the existing file each time it is called. This ensures there is no duplication or confusion with multiple versions of exported files having different cases, further minimizing the likelihood of users encountering case-related conflicts. Any potential confusion is minimal, as the success message clearly shows which file was imported, and users can easily avoid ambiguity by renaming files if needed.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Steps to reproduce:
exportcommand within the command box.import exportedcontacts.csv(note the lower case):Expected result: An error message telling me "The specified file does not exist"
Actual result: Success message telling me that the file has been successfully imported, with the lower case file name in the message, despite extracting information from the file with upper case name.
This case insensitivity is not mentioned in the UG, and might lead to incorrect behavior if the user actually has multiple .csv files with the same name, but different casing.