A feature can pass every functional test and still fail in production: the page crawls when a thousand people visit at once, or a crafted input exposes data it shouldn't. Performance testing and security testing look for those problems before real users or attackers find them.
You'll start with the main types of performance testing (load, stress, and spike) and what question each one answers. Then you'll run load tests with JMeter and k6, two widely used tools. On the security side you'll learn to scan an application for common weaknesses with OWASP ZAP, and meet the OWASP list of the most common web vulnerabilities.
With non-functional testing covered, you'll be ready for the next module, CI/CD & Test Pipelines, where you run all of these checks automatically on every commit.
The difference between the main types of performance testing, and which question each one is designed to answer.
A first load test in Apache JMeter: setting up a test plan, simulating users, and reading the results.
An introduction to k6, a developer-friendly load testing tool where tests are written as scripts, and how to view the results in Grafana.
How to use OWASP ZAP to scan a web application and spot common security vulnerabilities as part of your testing.