Skip to content
Jump to bottom

Removed Activity section, deprecated #9

Merged
merged 1 commit into from
Oct 30, 2019
+0 −9
Merged

Removed Activity section, deprecated #9

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 0 additions & 9 deletions exercises/03_acceptance/cucumber/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,15 +45,6 @@ This repository should already be setup to be ready to go, but if you ever want
"cucumber": "cucumber-js ./features -r ./steps" } </pre>
5. Put your gherkin files (.feature) in /features and cucumber files (.steps) in /steps.


# Activity

After you've wrapped your head around existing tests try giving "features/nextFeature.devel" a try. It accomplishes the same thing as our unit test, but instead checks the functionality at a higher level (acceptance/integration testing).

There are some instructions and support code already available in "steps/add_one.steps.js", you just need to implement the tests in the same way we did with our first Scenario.

Remember to have your website running in a different terminal if you want puppeteer to be able to access it.

# Notes

If you want to develop a new Scenario, or even a new Feature, just write the Gherkin tests first (the human readable tests), then try running them. They will obviously not pass, but the terminal will help you write them.
Expand Down