Allow adding invalid Email Address for `add` command

[choowengyan]

According to the screenshot below, the program allows adding invalid email address that does not follow the format of valid email address as stated in the UG.

For example, the program allow input of email address such as johnd@we without .com (which violates the standard email address format)

As shown in the program, error message did also mention that the domain should be separated by periods. However, the program did allow user to input domain without .com (which is invalid in real-world scenario)

[nus-se-bot]

Team's Response

Thanks for your report, but johnd@we is a valid email address according to the email address formatting standards, and the domain of an email address can be a local domain name with no top level domain.

Check out this stack overflow article that show many examples of how emails without a dot are still valid.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: [According to the team's response, I believe that the email address being tested (johnd@we) is still invalid according to the reasonings below:

1. According to the team's User Guide, it says that email address MUST follow standard email address format, with an example below clearly showing that the team's definition of standard email address contains 3 parts (in italic) separated by @ and . : username@domain.com

2. As shown in the bug report given above, the team has mentioned about the format of email address and its constraint in the application (specifically in the message box of the app), especially stated in point 2 where the domain labels is separated by periods. However, the tested email address domain is not separated by periods at all. This has clearly contradict with team's response on the definition of standard email address format.

2. This is followed by a '@' and then a domain name. The domain name is made up of domain labels separated by periods.

3. As shown in the screenshot below, it is clearly that the email address being stated is NOT a valid email address (tested using Gmail)

   ]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** [I believe that the severity of this issue can be considered as Medium, as it causes inconvenience to the user. Given a scenario where all the email address inputted in the application are not correctly checked (E.g. all emails inserted are without `.com`) , and when there is a need to bulk sending emails to the person in the list, all the emails sent will be bounced back, causing significant inconvenience to the user due to lack of checking for a **valid** email address format.  Email address is considered a very important field/ information for the context of this application as it is used to manage meetings and it will be the main channel to contact the person. Hence, I believe that solving this issue will make a significant improvement to the application. Screenshot below taken from teams's User Guide.  ]

---