📊 Monitoring

Monitoring in E2E Test Automation helps ensure your APIs are working correctly, all the time, without manual effort. It allows you to automatically run your API tests on a schedule, catching issues before they impact your users.

Whether you’re a developer, tester, or product owner, monitoring gives you peace of mind by alerting you to issues like broken endpoints, unexpected errors, or performance slowdowns.

📋 What is Monitoring?

Monitoring in E2E Test Automation acts like a watchdog for your APIs. It runs your test collections on a regular basis — even when you’re not around. If any issues arise — such as a wrong status code or a missing field in the response — it will notify you.

Instead of waiting for user reports or manually testing APIs, E2E Test Automation automates the process for you. It ensures your API works as expected without requiring constant attention.

🔄 How Does Monitoring Work?

Monitors in E2E Test Automation are built around API Collections. These collections are essentially folders that contain the API requests you want to test. Each request can also have associated test scripts that validate if the response is correct.

Workflow:

Create Your API Collection – Build your collection by adding the API requests and their associated test scripts
Link the Collection to a Monitor – Once the collection is created, link it to a monitor and set the schedule for when it should run
Choose the Environment – When setting up a monitor, choose the environment to use, such as Development, Staging, or Production
Monitor Runs – The monitor will:
- Use the collection to determine what requests to test
- Use the selected environment to determine where to send the request (e.g., production server or test server)
- Check if the response matches the expected results, using the test scripts

⏰ Scheduling: When and How Often to Run

One of the most powerful features of E2E Test Automation Monitoring is scheduling. You can set your monitors to run at specific intervals, ensuring your APIs are continuously checked.

Available Scheduling Options:

Every 5 minutes
Every hour
Once a day
On certain days or business hours

You can also set the time zone and start time, allowing you to schedule tests at the exact moments you care about — such as right after a deployment or every morning before business begins.

This eliminates the need for manual testing and ensures your APIs are checked consistently.

🔁 Retry on Failure: Avoiding False Alarms

Sometimes, API failures can be temporary — due to network issues, server restarts, or third-party delays. Instead of triggering an alarm immediately, E2E Test Automation allows you to enable retries.

Retry Options:

Number of retries – Set how many times the monitor should retry in case of failure (e.g., 1 or 2 retries)
Delay between retries – Set a short delay between retries to avoid immediate failure triggers

If a retry succeeds, E2E Test Automation treats the monitor run as a pass, reducing the chances of false alarms.

🧪 Test Scripts Power the Logic Behind Monitoring

Your monitor doesn’t just check if the server responds — it checks whether the response is correct. This is done using test scripts, which are small blocks of logic (in JavaScript) that run after each request.

Examples of Test Scripts:

Check if the response code is 200
Verify that the response body includes a specific user ID
Ensure that the token is not expired

When a monitor runs, E2E Test Automation evaluates these scripts. If any test fails, the monitor run is marked as a failure.

This ensures that your APIs are not just “alive,” but they’re working correctly as well.

🔔 Alerts and Notifications Keep You Informed

Monitoring is only useful if it keeps you informed when something goes wrong. E2E Test Automation lets you set up notifications to alert you immediately when a monitor fails.

Available Notification Options:

Email Alerts – Send alerts to your team’s email addresses
Webhooks – Post alerts to Slack, Microsoft Teams, or your own system

This way, you can act quickly and resolve issues before your users are impacted.

🎯 Why Monitoring is Important

Here’s why monitoring your APIs is a critical part of your API development and testing lifecycle:

Catches issues early – before they impact your users
Saves time – no need for manual checks throughout the day
Ensures reliability – APIs are always under continuous watch
Boosts confidence – you know exactly when something fails and why

Whether you’re testing internal APIs or public endpoints, monitoring helps you shift from reacting to problems to preventing them.

✅ Summary

E2E Test Automation’s monitoring features provide you with automatic, scheduled checks for your APIs, ensuring they perform correctly at all times. With flexible scheduling, environment-based configuration, and detailed test scripts, you can rely on E2E Test Automation to continuously check your APIs without needing to do manual testing.

Happy monitoring! 🚀