Skip to main content
All CollectionsTesting
Selecting groups and networks while configuring tests
Selecting groups and networks while configuring tests

This article explains how to configure tests for different networks and groups of sensors.

Updated over 5 years ago

When adding a new test, all groups, SSIDs and ethernet networks are selected by default. This means that if a test is added with this default configuration, it is applied to all groups, all sensors, all SSIDs and ethernet networks.

In order to add a new test to sensors in a specific group or network, click on the Change Selection button highlighted below. 

This will open expand into a list of sensor groups and networks currently configured on the dashboard. All the groups and networks are pre-selected by default.

To change this, uncheck the blue checkbox next to All Groups and select only the group of sensors you wish to configure the new test on.

When only one or some out of all the groups on the dashboard are selected, the numbers on the right-hand side of the network names change to indicate how many sensors will inherit the test config. For example, the group Conference Rooms is selected below. Under networks, the Cape Guest wireless SSID indicates 1/2, which means that one sensor (out of 2 total sensors testing that SSID) will inherit the new test configuration. To identify which sensor that is, hover the mouse pointer over the numbers 1/2 and a dialog box will display the name of sensors being configured. Similarly, 1 out of 3 sensors testing the Cape SSID will inherit the test config. 

Notice that in the video above, next to the Corporate SSID and Wired networks, 0 indicates that none of the sensors in the group Conference Rooms are testing these networks. So, they should be unchecked while adding a new test.

Below the group and network selection pane, the highlighted text confirms the number of sensors, groups and networks that the test configuration changes will be applied to – whether it is the addition of a new test or enabling/disabling a test already configured.

Read more about testing multiple networks

Did this answer your question?