In the previous demo, we used ZAP to do a spider scan and an active scan. The purpose of the spider scan is to explore all potential URLs and web resources. However, there are some web resources that will require manual guidance, such as authenticated resources, user registration, or the shopping business flows.
Therefore, we will need a web UI automation framework, such as Selenium, to guide ZAP through some of the web pages. A testing team who may previously finish the functional automation testing, it's suggested to apply the web security scanner, OWASP ZAP, in proxy mode to reuse the existing automation testing.
In this case study, we use the user registration flow as an example to demonstrate how to apply a Selenium automation framework and ZAP for web security automation testing...