Story validation workflow

Where to start?

1. Sign in to your JIRA workspace

https://academiatestarii.atlassian.net/

2. Go to the Projects section and select “Academia Testarii”

3. Select the Board where you want to work (either “Practice” or “Examen” final)
 Story validation workflow

4. Identify the Team which you are part of and open the Story you want to work on

5. Read the story’s summary, description and Acceptance Criteria.

- The goal is to understand what you will be ultimately testing.
- Identify the area of the site which is described in the Story (E.g.: On the “Home Page”, a
“Cursuri” section has been implemented)
- Read the Acceptance Criteria to understand what are the requirements for that Story to
be implemented. What should it contain? (e.g.: A button has been added that when
clicked, redirects the user to a new page)
-

6. Navigate to the Test Site(SUT) and find the area where the Story has been
implemented.
- The test site should be, based on the progress made, either ver1 / ver2 /
ver3.academiatestarii.ro
 Story validation workflow
- This is done to familiarize yourself with the current implementation (of the Acceptance
Criteria) and to do a visual inspection of the application. E.g:

7. Create Sub-Tasks in the story you are about to test

- Select “Create Sub-Task” from the “…” in the upper right corner of the Story window

- This is done in order to be clear to every member of the team:

o who is working on what
o what is the current progress
o how much more working hours there are left before the story is finished
- In a real-life working scenario, you will be part of a team of 5 up to 8 individuals. These
people occupy different roles (developer, manager, product owner, scrum master,
designer, and you, the software tester). Everyone will create sub-tasks in all stories in
order to know what needs to be done to finish the story and how much time it will take
them to finish it.
o A developer will probably create implementation tasks
§ E.g.: Write code; Review code; Write Unit Tests; etc.
o As software tester, we will create for each story we test, 2 tasks
§ Create Test Plan
§ Execute Test Plan

8. Create Test Cases to validate the Acceptance Criteria for your Story
 Story validation workflow
- Using the “+” button, from the left navigation menu, select Issue Type “Test”
- More tips on how to write tests cases in the “Cheat Sheet”

9. Link the Test Cases to the Story

- Select “Link” from the “…” in the upper right corner of the Test Case window and then
“This issue” -> “Relates To” -> Story ID

- This is done in order to have full visibility about every work item that is being done for a
Specific Story.
10. Add your Test Cases to a Test Cycle
- From the left navigational Menu, selects Tests -> Test Cycle tab -> Select the version
which you are testing on (ver1/ver2/ver3) and select “Create new cycle”
 Story validation workflow
- In the “Name” section, add the ID of the Story you are testing and your name (e.g.: “AT-
203 George”) and click “Create”
- Find you Test Cycle in the list, and from the right of the cycle, select the cogwheel and
“Add Tests” (add the tests you’ve written for the Story to the Test Cycle)

11. Execute the Tests from the Test Cycle

- Press the “E” button next to each test within the test cycle
- For each step, add a Status (“Pass”/”Fail”/etc.)

12. Log any Defects encountered

- More tips on how to log defects in the “Cheat Sheet”
13. Link any Defects found to the Story
- The link status should be “blocked” instead of “relates to”
14. Close your Sub-tasks from the Story
- From the “…” next to the sub-tasks you created, select “Done”.
15. That’s it.