| | |
|---|
| | | ## Big Picture |
|---|
| | | > From the previous exercise; we introduced pipeline-as-code and new Jenkins Slave nodes. This exercise focuses on extending the pipeline with Non-functional testin and some automated security testing. |
|---|
| | | |
|---|
| | |  |
|---|
| | |  |
|---|
| | | |
|---|
| | | _____ |
|---|
| | | |
|---|
| | |
|---|
| | | |
|---|
| | | 4. Click `add build step` and select `execute shell` and add the following to it, replacing `<YOUR_NAME>` as expected. We will just test the `create` and `show` API for the moment. We are grabbing the response code of the perf-test to keep Jenkins running both shells steps and then exiting with whichever fails: |
|---|
| | | ```bash |
|---|
| | | export E2E_TEST_ROUTE=todolist-api-<YOUR_NAME>-dev.apps.lader.rht-labs.com |
|---|
| | | export E2E_TEST_ROUTE=todolist-api-<YOUR_NAME>-dev.<APPS_URL> |
|---|
| | | npm install |
|---|
| | | set +e |
|---|
| | | npm run perf-test:create |
|---|
