Skip to content
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.

Sign up for GitHub

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

style: proofread manual testing section #40

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

style: proofread manual testing section #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 13 additions & 11 deletions exercises/01-manual_testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
# Manual testing

Manual testing is usually a part of test automation. We need to know the steps that are then going to
be automated.
Manual testing is usually a part of test automation. We need to know what the steps are
before we can automate them.

Let us first go through our System Under Testing (SUT) before we proceed.

## System Under Testing (SUT)

Our SUT is simple web application that is running at localhost:7272 address.
Our SUT is a simple web application that is running on `http://localhost:7272`.

Features:
### Features

- Index page contains login form
- The index page contains a login form
- Username: `demo`
- Password: `mode`
- Submit login form button
- After successful login the user is redirected to the welcome page
- User can log out after successful login and will be redirected to the login page
- After incorrect login credentials the user is redirected to the error page
- After successful login, the user is redirected to the welcome page.
- The user can log out after successful login and will be redirected to the login page.
- After incorrect login credentials, the user is redirected to the error page.

## Exercise

Expand All @@ -27,11 +27,13 @@ How would you manually test the successful login use case?
- Inside it add a text file, call it `login.robot` (note that `.robot` is the extension, not `.txt`).
- Write line by line, all the steps that you would need to perform if you were manually testing the login feature.

## Verify your results
## Verify your solution

After you've added steps that you think are needed to manually test login feature run:
After you've added the steps that you think are needed to manually test the login feature, run:

- in Windows: run command `python verify.py 01`
- in macOS/Linux: run command `python3 verify.py 01`

If the output is `Ready to proceed!` then you're good to go! Otherwise, the check the output about what is missing?
If the final output is `Ready to proceed!` then you're good to go! Otherwise, check the output to see what is wrong.

When you're ready, move on to the [next section](02-robot-syntax.md).