This activity is part of the run task flow.
Add devices to a run task
When adding devices to a run task, you have one of two options for tasks: one device or multiple devices.
Tasks with one device mean that the tester uses a single device when executing the tests. For example, a tester tests an app on the newest available iPhone.
Tasks with multiple devices are for scenarios where multiple devices interact. For example, when a tester tests casting a streaming app from their iPhone and to a Chromecast TV. Multi-device tasks are only available for manual tasks.
NOTE: A multi-device task doesn't mean that the same test is executed on several devices. For example, if you want your app tested on an iPhone and the same tests executed on an Android phone, you need to set up 2 single-device tasks.
Find devices from your project team
Select the run task where you want to add devices.
Click Add people or devices.
Click Devices, which opens the add devices modal.
The modal is made up of three areas:
Saved segments - previously saved segments of the devices and users in your team.
Segment filters - ways for you to filter out the devices you need based on multiple parameters.
Device preview - the list of devices and the people operating them who match these filters from your project team.Select whether you want to create a single or multiple device task.
Optionally click an existing segment to apply its filters or alter any filter.
The device preview shows you which devices can now be added. You now have two options:
Create a task manually
Use our dynamic allocation algorithm to compile a team for you
Manually invite a specific person with a specific device
Manual invites let you pick a specific person and device to complete your testing activity. This is great if you have specific requirements that you know a tester is equipped to fulfill. However, this also means more manual overhead for team compilation as you need to manually handle every case where a tester is unable to take on the work. Invite someone manually:
Select one or more devices in the device preview.
Click Add.
Dynamically add a person with a device
The dynamic allocation uses our Team Compilation algorithm to find the widest variety of available testing devices depending on the device requirements you have given through filters, the rest of the devices already used in the run, availability of testing resource and multiple other factors. It also automatically replaces any tester that is unable to complete the work to make team compilation a breeze. To allocate devices dynamically:
Describe the range of suitable devices using the filter definitions.
Select the number of devices that you want to complete the testing.
Click Add.
Create team segments
Available filters
We currently support the following filters:
Category - the device category e.g. mobile, tablet, gaming device, wearable.
Manufacturer - The company that manufactures the device, e.g. Apple, Samsung, Google, etc.
Model - The specific hardware model e.g. iPhone 7, PlayStation 5, Wear 2, etc.
Platform - Operating system and its version, e.g. iOS, Windows, Linux, Tiezen, etc. In addition, you can select the version range and whether to include beta versions of the release or only production versions.
Browser - Web browsers for testing. We currently operate under the model that browsers can be installed when needed. As such, browser selection doesn't limit available devices nor do we require our users to list what browsers they have installed on any particular device.
Organization - Whether the user is part of our Freelancer Network, Testlio employee, or member of the client's organization. This is useful for making segments of internal or network testers.
Tester - This filter allows you to make groups of specific testers. This is very handy if there are categorizations that don't exist on our platform or are not publicly available. E.g. as a client, you may want to create a segment for your developers, or in-house QA team. Our Testing Managers may custom curate network freelancer segments to match specific testing needs like payment testing or exploratory testers.
Languages - Languages that the user has listed on our platform that they are able to test in. This is useful for localization or other testing capabilities.
Countries - The geographic location that the device's owner is located in. This can be used to target testers for specific testing needs for streaming and analytics testing, as well as localization and location testing.
Filter-specific nuances
Browsers - If no browsers are selected, a specific browser isn't added. This is contrary to the device logic as if no device is selected, the system treats it as "any device is suitable" and picks one from all options. If selected, the browser info is also added to the work invite for Network Freelancers and shown in run results.
Languages - If no language is selected, a specific language for testing isn't added. If selected, the specified language is also added to the work invite for Network Freelancers and shown in run results.
What happens next?
If you are inviting someone from within the client organization and the run is scheduled, the user who was allocated to the task is immediately notified. They can then access the test execution once the run starts.
If you are inviting a freelance tester, they are invited to complete the work and, if they accept, can access test execution through their dashboard when the run starts.
In any scenario, the tester is shown the device they are expected to test with at the start of their test execution session. If they cannot test on that device for any reason, they can declare a different device to test with, but network freelancers need to coordinate this change with their run coordinator beforehand.