Tests are only useful if they actually run. In a real team nobody runs the whole suite by hand before every merge, so the checks are wired into a pipeline that runs automatically whenever code changes. CI/CD (continuous integration and continuous delivery) is the practice that makes this possible.
You'll start with what CI/CD means and why teams use it. Then you'll build a workflow with GitHub Actions that runs automated tests on every push and pull request, and see how a failed test blocks a bad change from being merged. Finally you'll look at Jenkins, a long-established automation server, and learn how a Jenkinsfile describes the stages of a pipeline as code.
With your tests running automatically, you'll be ready for the next module, Mobile & Cross-Platform Testing, where you extend your testing to mobile devices and different platforms.
A quick introduction to continuous integration and continuous delivery, and what a pipeline does between a code change and a release.
How GitHub Actions works: events, workflows, jobs, and runners, followed by a hands-on CI pipeline built from a workflow file.
Setting up a workflow that runs your automated tests on every change and only deploys when they pass.
Installing Jenkins, creating a pipeline, and writing a Jenkinsfile that builds a web application as a series of stages.