-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
* #11
Comments
Please link the GitHub repo Where should they find the signup.php, signup.css, and signup.js files? Tell the untrained user to enter the directory these files are stored in so they can easily find it. What do you mean by "Run the files"? What does this exactly mean? Is this step necessary? For tests 2 -> 4, before specifying what fields to enter or not to enter, direct them to the signup page. So step 1 should be a link that takes the untrained user to the signup page of the application. "A success message should show on the top of the screen". Specify what the exact success message would be, what would the text on the success message state? Add that to this test step. Need to add a test for attempting to signup with an email address or username that has been used already. What should the user expect to see when this case occurs? I see that you add a sentence for each test that describes what the test is, this was one of the reasons we lost points in last sprint, so lets remove that to not lose points again. |
No description provided.
The text was updated successfully, but these errors were encountered: