From 7b94ee60e46345f9900ee520e78b32f89668cda5 Mon Sep 17 00:00:00 2001 From: harjaus Date: Wed, 30 Oct 2019 13:58:42 -0700 Subject: [PATCH] Removed Activity section, deprecated --- exercises/03_acceptance/cucumber/readme.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/exercises/03_acceptance/cucumber/readme.md b/exercises/03_acceptance/cucumber/readme.md index 7ab4b6f..30f035f 100644 --- a/exercises/03_acceptance/cucumber/readme.md +++ b/exercises/03_acceptance/cucumber/readme.md @@ -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" } 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.