Running tests in batch

To get the result you typically run the whole set of tests as a batch, either manually or if you have premium account, on a scheduled basis. This part describes the results and how to run them manually. To set up a schedule, check the following instructions.

Manual run

Above the list of tests there is a button to run all tests in this set of tests. If the tests were already run as a batch before, you can see the last results' score. If you have a premium account, you can also see last 3 results and click through to see the detailed result output.

Waaila tip:
If you want to run only selection of the tests, you can select them by clicking on their checkboxes. The button will say "Run [n] selected" where [n] is the number of tests you selected.

run-tests

When you click on the button to run the tests, a view for test results is open where you can observe the progress on the progress bar on the top. All of the already processed test are displayed and added to the aggregate overview but you need to wait for the run to finish to see the complete results.

Test set results

When a set of tests has been run, you can see Performance of the test run as the share of the sum of realized scores for all tests (Score) and the sum of Max Scores for all tests (Max Score). On the right there are the counts of tests by the result status.

Below is a list of all included tests and their results, including the result status, realized score (compared to the Max Score possible for given test), and potential output messages and tables. The tests are sorted by their test code and can be filtered by the output type or by searching a part of their name.

In the example below the set has less than 50 % performance. Only two tests passed without issue. There are two minor issues (warnings) and two failed tests (the tests marked as info only return information without evaluating it). Two of the test details are seen below the aggregate overview. The first is a failed test that failed because one of the device categories (mobile) has lower session to user ratio than 1.05 (the resulting score is 0 out of 150 because the test failed). The second test passed because the event to session ratio is not too low, in particular not lower than 1.05 for any device category (the resulting score is full score, i.e. 150, because the test passed).

sample-results

Waaila tip:
To learn more about a test you have just run in batch, you can hover above the test's name to read the description or you can click on the name to open the test in a test editor (the test opens in the next tab of your browser).
On this page