search

mrweikiat / pe

0 stars 0 forks source link

No error thrown for invalid email address #9

Open mrweikiat opened 3 years ago

mrweikiat commented 3 years ago

tried command: add -n bob -e death_69@example Expected: error to be thrown because it is an invalid email with no .com Actual: Valid test case and was added to the list

image.png

image.png

nus-pe-bot commented 3 years ago

Team's Response

Not a bug.

image.png

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

invalid email inpiut

Email with no '.com' domain passes through. should handle it. Screenshot 2021-04-16 at 3.14.55 PM.png

[original: nus-cs2103-AY2021S2/pe-interim#2613] [original labels: severity.Medium type.FunctionalityBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Not a bug.

  • This format is intentionally accepted, see #245, e.g. tim@localhost
  • Severity = Low: Outside of normal use
  • Bug report type = FeatureFlaw: Behaviour is clearly specified in UG, see below.

image.png

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: tim@tim is not an email, so there should at least be error thrown for not following to the format of the email eg: USER_NAME@DOMAIN_NAME.COM . If not, tim@time.commm is also a valid input, tim@tim.com.sggg is also a valid input. Should handle these cases as well, since currently these emails are valid test cases

:question: Issue type

Team chose [type.FeatureFlaw] Originally [type.FunctionalityBug]

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

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

Reason for disagreement: [replace this with your explanation]