Use Cases with Scenario Steps
We can describe a web application in many ways:
- Functional Specifications
- Use Cases
- Scenario Steps, which are described on this page.
This page has examples that we use often.
Scenario: Sign In
- I go to the website www.my.com.
- I click the link "Sign In".
- I type my username and password.
- I click the button "Enter".
- I see my home page.
Scenario: View My Profile
- I sign in.
- I click the link "Profile"
- I see my profile.
- I see my status.
- I see my photo.
Scenario: Edit My Profile
- I view my profile.
- I click the button "Edit".
- I see the form.
- I see the text field "Update My Status".
- I see the button "Upload My Photo".
- I see the button "Save".
Scenario: Upload My Photo
- I edit my profile.
- I click the button "Upload My Photo".
- I see a file chooser.
- I choose a file.
- I click the "Upload" button.
- I see my new photo.
Why use Scenario Steps?
The steps are useful in several ways:
- During planning: the steps enable the business stakeholders to discuss the workflow.
- During programming: the steps show the programmers exactly what needs to be built.
- During quality assuranace: the team can reliably test the application step by step.
- During future upgrades: the future teams have a clear document of the workflow.
What's Next?
- Index Of Articles: Web Design & Development
- Functional Specifications Template
- Functional Specifications Tutorial
- Statement Of Work
- Use Cases
- Wireframes
- Cucumber scenarios consiting of steps "Given When Then"