Start building tests for the Login page by defining its two inputs.
Start with the User ID. Type Input into column 1 and User ID into column 2.
For the User ID, what could be some different choices?
- A good value is something in the form of a good email address.
Type in “good email address.” - Another is an empty value, as in nothing is filled into the box.
Type in “empty.” - Another could be a string that’s not in the form of an email address--a bad syntax user ID.
Type in “bad syntax.” - Our last choice is a value that’s too long. Ordinary users, of course, would never try to enter a 60-character user ID, but it’s just something like that that could break the application and so we need to test for it.
Type in “too long.”
Since the rules for forming good user IDs and good passwords are different, we’ll need a different set of choices for the password:
- Empty is one choice.
Type in “empty.” - To make sure that the user can’t enter a whole string of blanks make “long blank string” another choice.
- Of course there’s a good syntax choice.
Type in “good syntax.”
Notice that I put that one first. It’s generally our convention to put the good choices—the ones that lead to successful results—first in the list. You’ll see when we generate the tests that it causes the success scenarios to be the first ones in the test suite.
Finally, type in “Action” and then “Log In.” This line refers to the step where you click the Log In button.
Now it’s time to define the different choices for the User ID and the Password.
Save the file and close it.