Configurable aliases for failure categories

Set aliases for parent failure categories so your team’s terminology is reflected consistently across Test Reporting & Analytics.

BrowserStack Test Reporting & Analytics uses a fixed set of parent failure categories (Product Bug, Automation Bug, Environment Issue, and No Defect) to power Automatic Failure Analysis, Quality Gates, and platform-wide reporting. These categories are not editable by design to ensure accuracy and consistency.

With the Configurable Aliases feature, project admins can define a custom alias for each parent category at the project level. The alias visually replaces the default label across the UI. The underlying system category remains unchanged, preserving AI model accuracy, quality gate logic, and aggregation behavior.

Who can configure aliases ?

Only Project Admins can configure aliases for failure categories. The configuration is scoped to a single project.

Set an alias for a failure category

To set an alias for a failure category:

1. Navigate to Settings > Failure Categories for your project.
2. Locate the parent failure category you want to rename (for example, Automation Bug).
3. Click Add category alias.
4. Enter your alias in the Enter the alias name field next to the required failure category.
5. Click Add alias name.

Test Reporting & Analytics now shows the alias in place of the default category label across all supported views in the project.

Where do you see aliases?

Once configured, Test Reporting & Analytics shows the alias consistently across the following areas:

• Build Insights page: Category breakdown charts.
• Test Listing page: Test category labels and filters.
• Test Details page: Test category labels.
• Settings > Pattern Analysis: Failure category labels.
• Quality Gates: Configuration UI and status evaluation outputs.

API behavior

Every API response includes both the standard failure category and the configured alias as a dual-value payload, so integrations and downstream tooling that rely on standard category names continue to work without changes.

{
  "failure_category": "automation_bug",
  "failure_category_display_name": "Test Code Issue"
}

Points to remember

• Aliases are project-level settings. Each project maintains its own alias configuration independently.
• The underlying system category is never modified. AI-driven Automatic Failure Analysis, quality gate logic, and platform aggregations continue to use the standard parent categories.
• Custom failure sub-categories aren’t affected by this feature. Aliases apply only to the parent-level categories.

Related topic

Check out Automatic Failure Analysis to learn more about creating and managing custom failure sub-categories.