When using the Test Now feature, a test should be run from all the locations that have been selected for that monitor. Currently, the test only runs from one location.
There are two ways a test can be run now
From the Uptime Monitors (Overview) page
Using the Test now button
In Monitor Management
When adding/editing a new monitor, using the Run test button
When launching another test in the add/edit page (having already run one), using the Re-run test button
ACs:
When running a Test Now from Monitor Management (in any way as described above), the test should run in all locations that have been selected
The status of each run should be shown as each result comes in (e.g. it may be up from one location, down from another)
This needs to support all types of monitor (ICPM, TCP, HTTP and Browser)
When running a Test Now from the Uptime Monitors page, the test should run in all locations that have been selected
The IN PROGRESS status should appear until results from all locations (that are defined for that monitor) have come in
This is even if the page is refreshed / reloaded (by the user, or via the Kibana auto-refresh)
The current in n/n locations is misleading as it related to the Up and Down states - this should either be removed whilst the test is in progress or changed to reflect how many test location runs are in progress (whichever is simpler)
Once test results have come back for all locations, the left hand Status badge and the in n/n locations detail should change back to the typical behaviour (i.e. show Up or Down using the existing logic)
When using the Test Now feature, a test should be run from all the locations that have been selected for that monitor. Currently, the test only runs from one location.
There are two ways a test can be run now
ACs:
in n/n locationsis misleading as it related to theUpandDownstates - this should either be removed whilst the test is in progress or changed to reflect how many test location runs are in progress (whichever is simpler)in n/n locationsdetail should change back to the typical behaviour (i.e. showUporDownusing the existing logic)