RedHatTraining/rht-labs-docs.git

			@@ -37,7 +37,7 @@
			- Do some light performance testing to monitor throughput of APIs

			## Tools and Frameworks
			> Below is a collection of the new frameworks and tools that will be used in this lab
			> Below is a collection of the new frameworks and tools that will be used in this exercise

			1. [eslint](https://eslint.org/) - ESLint is an open source JavaScript linting utility originally created by Nicholas C. Zakas in June 2013. Code linting is a type of static analysis that is frequently used to find problematic patterns or code that doesn’t adhere to certain style guidelines. There are code linters for most programming languages, and compilers sometimes incorporate linting into the compilation process.
			1. [Zed Attack Proxy](https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project) - The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. Its also a great tool for experienced pentesters to use for manual security testing.
			@@ -191,9 +191,13 @@

			2. With this config in place run a build on Jenkins. To do this; commit your code (from your terminal):
			```bash
			$ git add .
			$ git commit -m "ADD - security scanning tools to pipeline"
			$ git push
			git add .
			```
			```bash
			git commit -m "ADD - security scanning tools to pipeline"
			```
			```bash
			git push
			```

			2. Check out the Blue Ocean Jenkins view for how the parallel stage is viewed!
			@@ -243,9 +247,13 @@

			3. Save the `Jenkinsfile` and commit it to trigger a build with some more enhancements.
			```bash
			$ git add .
			$ git commit -m "ADD - linting and coverage to the pipeline"
			$ git push
			git add .
			```
			```bash
			git commit -m "ADD - linting and coverage to the pipeline"
			```
			```bash
			git push
			```

			3. When the build has completed; fix the linting errors if there are any and commit your changes. Look in Jenkins log for what the issue might be....