Which set of test scenarios should you configure for validating an email address?

Which set of test scenarios should you configure for validating an email address?

• A. Invalid email without @, invalid email address: null, valid email address: jane.doe@example.com
• B. An invalid email address that is missing the @ character; an invalid email address: null; a valid email address: jane.doe@example.com
• C. Invalid email address with spaces; invalid email address: null; valid email address: jane.doe@example.com
• D. Null email; valid email address: jane.doe@example.com; invalid email address missing @ character

Answer: (B)

When validating an email address, test scenarios should cover common invalid formats, the possibility of no input, and a valid example. Including an invalid email that is missing the @ symbol ensures the validator rejects inputs that lack essential structure. Including a null input checks that the function handles absence of data gracefully without errors. Including a known valid email like jane.doe@example.com confirms the validator accepts correct formats and returns a positive result. Other sets might miss one of these critical paths, such as not testing a null input or not including a clearly invalid format, which leaves gaps in how well the validation logic handles real-world cases.

When validating an email address, test scenarios should cover common invalid formats, the possibility of no input, and a valid example. Including an invalid email that is missing the @ symbol ensures the validator rejects inputs that lack essential structure. Including a null input checks that the function handles absence of data gracefully without errors. Including a known valid email like jane.doe@example.com confirms the validator accepts correct formats and returns a positive result. Other sets might miss one of these critical paths, such as not testing a null input or not including a clearly invalid format, which leaves gaps in how well the validation logic handles real-world cases.