Last updated: Nov 19, 2020 16:42
2 | Select a device
On the landing page, click OPEN DEVICE.
In the Manual Testing view, find a device you want to work with.
By default, the Manual Testing view opens in tile view
, but you can switch to a row view if you prefer.If you have been here before, you can select Recent in the left pane and choose a device you worked with previously. At any time, you can sort by manufacturer or use the search box at the top right if there is a specific device you would like to use.
Do one of the following:
To select a mobile device:
Make sure one of the mobile device folders is selected on the left, and then select the mobile device you want to test on to display the details pane on the right. This pane provides details on the device, such as availability, OS version, device ID, or location, and available capabilities.
On the device tile or in the selected device row, click OPEN.
To select a web device:
In the left pane, click the Web folder.
Click OPEN NEW WEB SESSION.
In the Open new web session panel, select the operating system type and version, the browser type and version, the resolution, and the location. If you want to use.
At the bottom, enter a URL to test.
To view Selenium capabilities generated for the selected configuration in all supported languages, click View capabilities.
You can copy those capabilities and use them in your scripts. To view the capabilities when the session has started, click the information icon in the right vertical toolbar.
Click OPEN.
3 | Test your app
The device session opens on a dedicated tab. Now you can begin testing on the device. For information on the testing functionality available in the public cloud, see Public Cloud updates.
Expand the option that corresponds to the testing you want to perform.
4 | View test results in a report
To view test results in a report, from the top menu, select Test Analysis.
The Test Analysis view presents your test results on the following tabs that present different views of the result data:
- CI Dashboard: Displays the history of the test results, grouped based on the CI jobname identifier. Here, you can track your CI/CD pipeline and scheduled builds/jobs.
- Heatmap: Displays a graphic overview of different cross-sections of the test results. You can group test results by two levels of characterizations – devices or specific tags. The different groups are color-coded based on the distribution of passed or failed tests.
- Report Library: Displays a list of all single test reports for the Perfecto Lab, along with recorded videos and screenshots. You can filter the listing to focus on a set of tests with a particular tag or drill down to view the full report. The tags may be execution-level context tags or specific test tags. You can also export reports in PDF format or as JSON data.
- Live Stream: Displays a list of test executions currently in progress and allows you to stop one or more executions at once if needed.
In addition, you can drill down to view the Single Test Report (STR) for a specific test. You can also export the generated Execution Summary or Single Test report (optional) as:
- A PDF report
- JSON data that can be formatted (using the Public API)
For more information, see Access and navigate the Test Analysis UI.
5 | Perform administrative tasks
Now that you have explored how manual testing works in Perfecto, let's take a quick look at how you can set up your team. The tasks in this step are typically performed by a user with an administrative role. They include adding members to your team, creating org groups and adding members to org groups, and adding roles.
Groups are useful for organizing users within Perfecto, for example by manager, project, or other criteria that work well for your team. Groups do not impact a user's access privileges within Perfecto. Those are controlled by roles.
Roles allow an administrator to determine the level of access a team member has within Perfecto. The roles available to your team are determined by the Public Cloud Package you have purchased. Standard roles might include:
Administrator: The Lab Admin with full privileges for your Perfecto Public Cloud. This would be a good role for the team lead or manager that is responsible for overall access to the Perfecto Public Cloud environment
Handset Viewer: A typical Perfecto user. This role allows a user to perform manual tests, view and stop executions, and view reports.
For more detailed information on these administrative tasks, see Manage users.