Even though the tests
are assigned to both Mobile Users and Remote Sites, the priority
in which the tests are pushed to the device is important particularly
to the remote sites, since each device in a remote site is capable
of running a different number of tests depending on the device size.
So, if you have created a test, for example Test A which has a priority
of 8, and attached it to multiple remote sites all of which can
run Test A, if one of those sites, for example San Jose, has reached
its limit on how many tests it can run, Test A will not be pushed
to the site. That remote site (San Jose) will get moved under the
Excluded
Remote Sites
column. But if you absolutely must run
the Test A, you can change the priority of Test A from 8 to a higher
location in the table, for example to the top of the list by clicking
on the dots to the left of the check box and dragging and dropping
it to the top of the list. Alternatively, you can select its check
box and click the up arrow at the bottom of the page. You will see
its priority change only after you click
Save
.
Now Test A will get a higher priority and will be pushed to the
San Jose remote site before the remaining tests that follow Test
A in the table. This would mean though that the San Jose remote
site will now be excluded in the configuration push from some other
lower priority test (lower priority compared to Test A) that is
pushed to it.