The Browser Health Report in Functionize provides a breakdown of testing metrics by browser. It allows teams to quickly see how tests perform across different desktop and mobile browsers, helping identify failures caused by browser-specific issues.
This report is especially valuable for ensuring cross-browser compatibility and maintaining high-quality testing standards.
Filters
Project Filter
- Use the Projects dropdown (top left) to select one or more projects.
- Narrow the report to a specific set of projects or select all projects for an organizational view.
Note: Selecting all projects gives a broad perspective on overall browser health across your Functionize account.
Date Range Filter
- Select a date range to view test health for a specific period.
- Confirm → apply the filter.
- Reset → clear the filter and return to default.
Browser Health Report Overview
Test Status by Browser
- Displays the number of test cases with the following outcomes across each browser:
- Passed: Green
- Failed: Red
- Warning: Yellow
- Incomplete: Purple
- Clicking on any status opens a detailed report.
Detailed Status View
When you click a status category (e.g., Failed), you’ll see a detailed report for all projects within the selected date range.
Report Includes:
- Project Name
- Test Name
- Created By – who created the test case
- Executed By – who ran the test
- Orchestration Name – if executed in an orchestration
- Execution Method – executed by Client or Functionize Support
- Execution Date/Time
- Status by Browser – color-coded results with Last Run status
Each status icon is also a link to open the specific test case in a new tab.
Download Option: Export the detailed report as a .csv file via the download button.
Test Executions by Browser
- A graphical chart shows the number of test executions across all active browsers for the selected date range.
- Helps teams compare execution volume and distribution across environments (e.g., Chrome vs. Safari vs. mobile).
Why Use the Browser Health Report?
- Quickly Identify Issues – Spot failures tied to specific browsers.
- Improve Coverage – Ensure your application works consistently across environments.
- Validate Compatibility – Detect cross-browser inconsistencies early in the testing cycle.
- Support Decision-Making – Provide stakeholders with data-driven insights into browser-specific risks.
Best Practice: Review this report regularly to track browser-specific trends. For example, if a test consistently fails on Safari but passes on Chrome, this points to a browser compatibility issue worth prioritizing.