How was automated testing organized within CI/CD in your last project?

In my last project, automated testing within CI/CD was organized as follows:

1. Each commit to the repository triggered a pipeline in the CI system (e.g., Jenkins, GitLab CI, or GitHub Actions).
2. Unit tests written in the appropriate language (e.g., pytest for Python) were automatically run in the pipeline.
3. After successful unit tests, integration and functional tests were executed to verify component interactions.
4. For UI testing, Selenium/WebDriver was used, running in an isolated environment (Docker containers).
5. Test results were collected and displayed in reports, and if tests failed, the pipeline was stopped and the team was notified.

Thus, automatic code quality checks were ensured at each development stage and before deployment.