Page tree
Skip to end of metadata
Go to start of metadata

Last updated: Nov 08, 2018 09:23

ReleaseUpdates
18.13
  • DigitalZoom extends support for Custom Fields defined by the tester - You can now use the Custom Field values to group the test reports for both the Heatmap and ReportLibrary views.
18.11
  • Updated Ruby and Python DigitalZoom SDK implementations -
    • Support for Custom Fields both at Execution and Test levels
    • Support for branch-name in CI Job specification
18.10

Improved usability features including -

  • Go directly from CI Dashboard to a focused Heatmap view using the new icon () that appears in the rightmost column or in the history/duration tooltip.
  • Use the Device ID as the factor for grouping the Heatmap areas, to easily identify if particular devices are affecting the test results
  • Optional Report Library columns list the Job information (Job name, Job number, and Branch) for the test instance.
  • Filter the tests displayed in the Heatmap or Report Library based on Custom Fields defined for the test instance.
18.5
10.13
  • Single Test Report View includes a quick link to activate the device, used in the test, in a new interactive Perfecto Lab session. This might be used to check whether an error situation can be replicated and better analyzed by manually operating the device.
  • JavaScript Reporting SDK extends support to include Custom Fields support as part of the PerfectoExecutionContext and TestContext. The Custom Field data appears in the execution report and may be used to filter the test reports.
10.12
  • Filter the list of tests by tags directly from the tooltip that lists the tags related to a test in the Report Library grid. See the article for more information.
10.11
  • Report Library Grid display supports adding a column to show the Device ID of the device(s) used for the test run.
10.10
  • TestContext class supports CustomField information. This information is defined as a set of <name, value> pairs and can be used to better identify and filter the test reports, by whatever parameter the testers which to add.
  • Job information of the ExecutionContext supports a FeatureBranch identifier, in addition to the Job Name and Number information. This allows the tester to run and identify separate tests for different branches of the tested application.
  • The Single Test Reports (STR) support a history graph for the single test that supports selecting any of the five nodes to navigate to the particular test execution report.
10.9
  • Report Library (grid) view includes a display of the history of each test report in the grid. Hovering over the nodes in the history supplies high-level information on the test instance.
10.7
  • DigitalZoom reporting supports creating JIRA Bug reports with all configured fields displayed and editable.
10.6
  • CI Dashboard displays the duration history for the past eight jobs. Corresponds to set of jobs in the result history.
  • DigitalZoom reports show list and details of all devices associated with a multi-device test job. Video of the test run, in STR, will show the flow on one of the devices, however, screenshots will show all devices.
  • Use DigitalZoom Reporting with your NightwatchJS test scripts. See a sample in the GitHub repository that uses the Reporting SDK to define the report tags and test steps.
10.5
10.4
  • CI Dashboard - support of drill-down from CI Jobs to Report grid, by clicking on history bars or subgroup of the latest build.
  • Flag the Assertion steps and checkpoint commands with a status flag.
  • Report Library view left panel can be adjusted in width to show all text associated with different groups.
10.3
  • New: CI Dashboard lists test-run history according to CI Job Names for easy access.
  • Support for JIRA integration to directly open and track JIRA issues from the Single Test Report.
  • Support for the Circle CI tool. See an example test suite configured for the tool.
  • Refined commands for Logical Step labeling and reporting
    • Start step and End step commands to provide information on the two ends of a logical step.
    • Assert to provide validation information at points of interest.
  • Support for all language platforms (C#, JavaScript, Python, and Ruby) have been updated to support all of the latest features.
10.2
  • Limitation: When using the Test start command in Native Automation scripts, if you supply the Job Name value then also supply a Job Number. If only one of these is supplied, an error is reported on the Test start command.
10.0
  • Fixed - Users with usernames that are substrings of other usernames can now update their user information.
  • Perfecto Native Automation scripts now generate Reporting formatted reports, supporting tags and steps. Use the "test start", "test step", and "test end" functions available in the Reporting group of functions.
9.8
  • Provide support for Slack notifications, from your Jenkins process, that include the URL of the Execution Summary Report for each test execution. Learn more.
  • Summary Report information, from the Public API, includes MCM identification and the list of relevant artifacts per test.
  • Execution Center links the different executions directly to Execution Summary Report.
9.7
  • Visual Analysis steps reported with both the "expected image" and the actual screenshot.
  • Reports for executions older than 45 days are no longer accessible.
  • Report dashboard tag filtering now supports ability to exclude reports with specified tags from the list of reports.
9.6
  • Public API to retrieve Execution Driver Report and Single Test Report data in JSON format. All attachment information included in the JSON information and can then be formatted by the user.