| exercises/2-attack-of-the-pipelines/README.md | ●●●●● patch | view | raw | blame | history | |
| exercises/3-revenge-of-the-automated-testing/README.md | ●●●●● patch | view | raw | blame | history | |
| exercises/images/exercise2/dev-pipeline-view.jpeg | patch | view | raw | blame | history | |
| exercises/images/exercise2/dev-pipeline-view.png | patch | view | raw | blame | history |
exercises/2-attack-of-the-pipelines/README.md
@@ -622,7 +622,7 @@  5. You should now see the pipeline view. Run the pipeline by hitting run (you can move onto the next part while it is running as it may take some time).   ### Part 5 - Backend Pipeline > In this exercise we will use the Jobs created for the `todolist-fe` as a template to create a pipeline for the `todolist-api` app by copying the config. @@ -729,8 +729,6 @@ ## Additional Reading > List of links or other reading that might be of use / reference for the exercise - What's in a package.json? ## Slide links
@@ -109,7 +109,7 @@ 2. You should see an output similar to the following. The above command has run a test suite for every `*.spec.js` file. The table generated in the terminal shows the code coverage. We're going to be focusing on the unit tests for now.  2. Repeat the same process for `todolist-api` and verify that all the tests run. There are 2 Api test files: `todolist-api/server/api/todo/todo.spec.js` & `todolist-api/server/mocks/mock-routes.spec.js` 2. 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. ```bash $ cd todolist-api $ npm run test exercises/images/exercise2/dev-pipeline-view.jpeg
Binary files differ
