liujiayue314 / pe

0 stars 0 forks source link

Examples no under the corresponding reasons #5

Open liujiayue314 opened 1 year ago

liujiayue314 commented 1 year ago

e.g. example 3 and 4 is about no multiple consecutive of special characters, example 5 is about no special characters is allowed at the start, but examples are all put in a list -> users might find it hard to indentify the reasons as to why the examples are not allowed/allowed

image.png

soc-pe-bot commented 1 year ago

Team's Response

Based on the information provided, it appears that the examples in the list clearly state the specific restrictions for email input in a concise and organized manner. Each example is labeled with a corresponding number and a clear statement on whether it is allowed or not allowed. Additionally, the reasons for why certain examples are not allowed are also provided.

While it is possible that some users may find it difficult to identify the reasons behind each example, it is important to note that the overall organization and labeling of the list serves as a useful reference for users to quickly check if their email input is valid or not.

Therefore, we believe that the current format and organization of the list is appropriate.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The format is misleading. The first time I saw this, I mistakenly thought that all the examples are for Allowed special characters for email are + , _ , - , . as they are listed directly under it. Only upon closer scrutinity, that I realize these is a consolidated list of examples for all the restrictions on email parameters.

Additionally, the reasons for why certain examples are not allowed are also provided. -- While it is true that the reasons are provided, users have to take some time to tell which examples correspond to which reason

it is useful reference for users to quickly check if their email input is valid or not. -- It is unlikely for users to check based on the list, as most users will simply input it in the programme to see if it is valid.

It would be much clearer if it was written like that.


## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]