How is test monitoring configured? Who monitors, are there schedules, on-duty shifts?

Test monitoring usually includes several components:

• Automatic test execution via CI/CD (e.g., Jenkins, GitLab CI).
• Results reports with test details (Allure, TestRail).
• Charts and metrics — execution time, number of failed tests, stability trends.
• Notifications in case of test failures — via email, messengers, or incident systems.
• On-duty shifts — assigning responsible persons who monitor test status and respond promptly to failures.

For example, in a QA team, there might be a duty schedule where someone is responsible for monitoring each day, checks the charts, and initiates problem investigations if necessary.