From 502af37fb08a5faf6be35f7862ee224bdebc9c3d Mon Sep 17 00:00:00 2001
From: Ravi Srinivasan <rsriniva@users.noreply.github.com>
Date: Fri, 15 Mar 2019 06:58:31 +0100
Subject: [PATCH] Merge pull request #1 from kborup-redhat/patch-1

---
 exercises/3-revenge-of-the-automated-testing/README.md |   34 ++++++++++++++++++++++++++++------
 1 files changed, 28 insertions(+), 6 deletions(-)

diff --git a/exercises/3-revenge-of-the-automated-testing/README.md b/exercises/3-revenge-of-the-automated-testing/README.md
index 532a65c..714f5ce 100644
--- a/exercises/3-revenge-of-the-automated-testing/README.md
+++ b/exercises/3-revenge-of-the-automated-testing/README.md
@@ -119,10 +119,10 @@
 
 4. Repeat the same process for `todolist-api` and verify that all the tests run. If you have an ExpressJS server already running from previous exercise; you should kill it before running the tests. The `mocha` test suite will launch a dev server for running the tests. There are 2 API test files: `todolist-api/server/api/todo/todo.spec.js` & `todolist-api/server/mocks/mock-routes.spec.js` for our API and the Mocks server. Remember to start the `mongo` container before running the tests
 ```bash
-npm run mongo:start
+cd todolist-api
 ```
 ```bash
-cd todolist-api
+npm run mongo:start
 ```
 ```bash
 npm run test
@@ -519,7 +519,7 @@
       // TODO - FILL THIS OUT IN THE EXERCISE
       this.$store.dispatch("updateTodo", {id: this.todoItem._id, important: true});
       console.info("INFO - Mark todo as important ", this.todoItem.important);
-    },
+    }
 ```
 
 14. Let's connect the click button in the DOM to the Javascript function we've just created. In the template, add a click handler to the md-button to call the function `markImportant()` by adding ` @click="markImportant()"` to the `<md-button>` tag
@@ -531,7 +531,7 @@
     </md-button>
 ```
 
-15. Finally - we need to make it so that when a new todo item is created it will have an important property. Head to `store/actions.js` and add `important: false`  below `completed: false` in the `addTodo(){}` action.
+15. Finally - we need to make it so that when a new todo item is created it will have an important property. Head to `src/store/actions.js` and add `important: false`  below `completed: false` in the `addTodo(){}` action.
 
 ![fe-add-actions-important](../images/exercise3/fe-add-actions-important.jpg)
 
@@ -677,11 +677,33 @@
     ![if-e2e-step3a](../images/exercise3/if-e2e-step3a.png)
 
 6.  Write the following test code. The pauses allow for the body of the page to render the todo list before exercising the test code:
-
+```javascript
+module.exports = {
+    "Testing important flag setting": browser => {
+      browser
+        .url(process.env.VUE_DEV_SERVER_URL + '/#/todo')
+        .waitForElementVisible("body", 5000)
+        .pause(5000)
+        .click('#clear-all')
+        .pause(2000)
+        .setValue('input',['set a todo',browser.Keys.ENTER])
+        .pause(2000)
+        .assert.elementPresent(".important-flag")
+        .assert.elementNotPresent(".red-flag")
+        .click('.important-flag')
+        .end();
+    }
+  };
+```
     <!-- ![if-e2e-step4](../images/exercise3/if-e2e-step4.png) -->
+    
+    <!-- ![if-e2e-step4](../images/exercise3/e2e-code-listing-full.jpg) -->
+
+7. Your final E2E test should look like the following:
+
     ![if-e2e-step4](../images/exercise3/e2e-code-listing-full.jpg)
 
-7.  At this point we should have a working e2e test. We can run this by using `npm run e2e`. When all tests pass, we can push up these changes.
+8.  At this point we should have a working e2e test. We can run this by using `npm run e2e`. When all tests pass, we can push up these changes.
 
 ```bash
 git add .

--
Gitblit v1.9.3