Hi
In your scenario, one of these methods might work for you:
Clone master Test Cases
1. Create your master Test Cases that contains the test steps (which are always the same for every device tested). Let's say you have 10 tests in total
2. Clone all 10 tests and assign those to a Test Cycle for Device #1
3. Repeat for Device #2, etc.
Advantage: enables you test all devices, but keep device results & issues separate from each other (because they are in different Test Cycles)
No-Clone Master Test Cases
1. Create your master Test Cases that contains the test steps (which are always the same for every device tested). Let's say you have 10 tests in total
2. In the Test Player, execute the first test and record the device being tested using either the Environment or Iteration fields (which you can customise in Configuration), or, create a custom field with a drop-down of values you decide
3. When the tester has finished testing Device #1, they click the "Start new execution" button in the Test Player to execute the same test script on a different device (recording that device in whichever field you decide to use)
Advantage: all tests are executed in 1 Test Cycle
There might be other ways of doing this but these are two that spring to mind and would be how I approach this use case.