Skip to content

Commit 125e022

Browse files
rodolfoprrReenaRajani
authored andcommitted
Add Acceptance Tests Kata (#45)
1 parent 861cbba commit 125e022

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

katas/acceptance-tests/README.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Acceptance Tests
2+
3+
## Problem Description
4+
5+
"Acceptance tests are created from <a href="http://www.extremeprogramming.org/rules/userstories.html">user stories</a>. The customer specifies scenarios to test when a user story has been correctly implemented. A story can have one or many acceptance tests, what ever it takes to ensure the functionality works.
6+
7+
Acceptance tests are black box system tests. Each acceptance test represents some expected result from the system. Customers are responsible for verifying the correctness of the acceptance tests and reviewing test scores to decide which failed tests are of highest priority. Acceptance tests are also used as regression tests prior to a production release."
8+
9+
From: http://www.extremeprogramming.org/rules/functionaltests.html
10+
11+
### 1. Choosing website to be tested
12+
13+
- <a href="https://github.com/gothinkster/realworld">RealWorld</a>
14+
15+
### 2. Writing user stories
16+
17+
- <a href="https://www.mountaingoatsoftware.com/agile/user-stories">User Stories</a>
18+
19+
### 3. Writing tests
20+
21+
#### Tests runners
22+
23+
- <a href="https://www.protractortest.org/#/">Protractor (JavaScript)</a>
24+
- <a href="https://www.cypress.io/">Cypress (JavaScript)</a>
25+
26+
#### BDD
27+
28+
- <a href="https://cucumber.io/">Cucumber</a>
29+
30+
### 4. Testing in multiple browsers
31+
32+
- <a href="https://www.browserstack.com/">BrowserStack</a>
33+
- <a href="https://saucelabs.com/">Sauce Labs</a>

0 commit comments

Comments
 (0)