Today Rigor is launching a new workflow for testing checks that is faster, easier, and more comprehensive. While improving how users can test a check sounds boring and unsexy, it actually provides a ton of value.

Why? Simple. Customers get more value out of performance monitoring when they have more comprehensive checks. For example, monitoring the performance of an entire checkout process is often more valuable than just testing a single page. Similarly, monitoring and alerting with different types of thresholds and assertions, such as start render or content size, is more valuable than just tracking page load times.

You can’t build holistic, comprehensive checks that monitor your site for multiple metrics without a fast, seamless, and easy-to-use process to verify the check and its thresholds are actually working.

With this new testing workflow, we improved on three areas of the testing process:  where we run the test, how we present the results, and what control you have over the testing process. We are launching this new workflow for testing our API Checks and will be adapting it to our Real Browser Checks and Uptime Checks in the coming months. Let’s take a tour of the improvements we have made.

Testing for the Right Locations

When testing a check, you can now specify the test location from a dropdown next to the Test button, as shown below:

test-check-locations Rigor Test Check

This is helpful for two reasons.

First, some APIs can vary their responses based on the geographic region. For example, an API for a service in Asia may return different results or an error if you are accessing it from a system outside of Asia. By allowing you to define the testing location, we are ensuring that you can properly test your checks.

Second, test location can matter when you are using response time as part of the success criteria for the check. As an example, imagine you are creating an API Check to run against systems in Europe. As we discuss in our API’s in Action ebook, APIs should be tested to ensure both the functionality of the response and the performance. Following this advice, you should configure the check to assert that responses come back within a reasonable time threshold as a step in your API Check, as shown below:

api-check-timing Rigor Test Check

By specifying a test location in Europe, you can ensure that the timing thresholds you set are accurate and the test is working properly.

More Control Over the Testing Process

While testing a check, you now have more control over the process. Specifically, we changed the UI to now show you how long the test has been running as well as provide 1-click actions to stop and re-start a test, as shown below:

test-check-stop Rigor Test Check

This helps streamline the “configure check, test check, modify check” cycle that happens when creating checks.

Seeing All the Results

We improved the UI for the results of a test as well. We reused the UI from our API Check, allowing you to page through the test results of each step of the check. If the test reveals an error, we jump directly to the failing step so you can see where your API is failing the success criteria.

test_fail Rigor Test Check

We provide all this data, regardless of whether the check passes or fails. This allows you to dig in to a successful run and decide what additional thresholds or assertions you may want to add.

good-test Rigor Test Check

Rigor: Powered by Customers

Our new test check workflow was the direct result of feedback we got from our customers.

Are you a Rigor user? Do you have ideas on ways we can improve the product? We want to hear from you! There are two ways to reach out:

  1. Book a call. Use this super fast and easy Calendar link to schedule a time that works for you to speak directly with Rigor Product Management. Tell us what you like and what we can do better. While we’re on the call we will share a sneak peak of some of the new features we’re working on now.
  2. Post on our Rigor Idea Exchange. See what other users are asking for, vote up suggestions, and share your own requests. When Rigor Engineering picks up a feature for development from the Idea Exchange, everyone who submitted or voted on a suggestion will get an email notification, so this is a great way to stay on top of the development progress of the features that matter most to you.

Interested in monitoring your sites, apps, and APIs for performance issues? 

Suggested Blog Posts

The Perception Gap for Poor Web Performance

E-commerce revenue continues to grow,as consumers turn away from shopping in brick-and-mortar stores to shopping online.  However, many businesses are not prepared for this growth because they do not fully understand the market and how to invest in...

Read More

Using Browser Trends to Maintain a Better Site

Because of the multifarious nature of web clients today, it’s important to consider the usage statistics when designing, implementing, and managing your site. However, misconceptions often arise when determining what browsers to design for an...

Read More

Finding Causes of Intermittent Errors from Google Webmaster Tools

Google Webmaster Tools is a web service that allows webmasters to view the status of their sites as seen by Google and the Googlebot crawlers. In addition to indexing your site structure and content, the Googlebot crawlers also record data on perform...

Read More

Optimization Options not Always Optimal

Web designers and developers are always looking for ways to speed up their page load times. Yahoo has an excellent article written on the best practices for speeding up your page. How do you know if implementing one of their suggested practices will...

Read More