Test Runs
The Test Runs tab (B) allows you to create new test runs (2) and see information about existing test runs. The header (1) shows which space and status options (3) have been selected. Hovering over a test run name provides access to browse, edit and delete functions. Clicking a test run name displays test run details.
The details include the contexts (platforms) selected and next and last launch dates and times. If a test run does not have a next launch date, its status is considered to be inactive (4).

You can also see disk space used, number of times launched, and total run time for all launches (5).

Hovering over the space name provides access to browse, edit and delete functions for the space that the test run belongs to.

To Create a New Test Run:

Click the ‘Add new test run’ button (see (2) above).
Select the space name (A).
Type a test run name (B).
Select an executable file from the files you uploaded (C).
Select platforms - operating systems and browsers you want tests to run on (D).

With 'Selenium nodes per platform' (F) you can run tests in parallel. You are expected to use one of the libraries, like TestNG or JUnit*, and your tests are grouped in threads. For example, using TestNG notation, your testng.xml thread-count value will match Nerrvana 'Selenium nodes per platform' selection.

You can read more about running parallel tests in Nerrvana here.

There are two options (E) for running your tests.
Option 1 allows you to launch tests immediately after saving your selections (1). We recommend validating your code first, without launching tests, to make sure they will run on Nerrvana.

Option 2 allows you to create delayed start and periodic launches, which can be used as part of a continuous integration process, or for functional monitoring of a SaaS system with Selenium.

For example, you can set a process which sets your application under test at 21:00 and uploads the last version of tests to Nerrvana and have a schedule set in Nerrvana to launch tests at 21:30. Or you can have a Selenium suite of tests to perform key checks on your live system every 10 minutes.
You can specify a start date (2) and time to schedule a future test run, as well as add parameters (3, 4) to set up a periodic schedule.

The hint (7) tells you the times of the next two launches to make sure you set it up correctly.

You can pause and resume test runs using option (6), or from the Dashboard (8). Skipped executions 'S' (9) are ones which were not launched because you paused a scheduled test run and the time of its start has passed.

If, for example, you're using Nerrvana for monitoring and want to upgrade your web application, you can pause a test run, complete the upgrade, upload an up-to-date version of tests, if necessary, and resume.

If you set a periodic schedule, Nerrvana shows you the next three executions on the Dashboard.
You can monitor test run execution progress on the Dashboard, but be aware that you have to refresh the page to see changes. 'N' tells us that our test run is scheduled next and that it's about to start (A). As the execution proceeds, the 'N' changes to 'R' to indicate that it's running (B) and then to 'OK' (C). Eventually, all of the icons will read 'OK' (D), which means that the tests were successfully completed.

Note: OK status only indicates that Nerrvana has successfully executed the tests. It doesn't mean that the tests haven't found problems.

However Nerrvana provides a simple way of bringing actual test results to its UI with a concept of 'messages'. You can read about it here.

* - these are not the only options to parallelize test execution. For example, there is Testoob in Python.