> ## Documentation Index
> Fetch the complete documentation index at: https://help.loopiq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Test Automation and External-Resource Analytics

## Open Test Automation Analytics

1. Open LoopIQ Analytics.
2. Select `Test Automation`.
3. Set the organization, team, application, release, environment, and time filters that apply to the review.
4. Select `Refresh` after changing source data or filters.

Choose the dashboard that matches the decision:

* `Executive posture`: trustworthiness of the current automated-quality signal
* `Execution reliability`: failures, stalls, duration, and risk queue
* `Coverage & traceability`: requirement assertions that are covered, partial, proposed, or missing
* `Evidence & governance`: governed, release-scoped, certification-scoped, diagnostic, and integrity-hashed evidence
* `Test asset health`: dependable, fragile, draft, approved, and healing-dependent assets
* `Maintenance health`: automation debt and proposed maintenance work
* `Provider & environment`: framework, provider, execution path, and environment performance

Dry runs are diagnostic and must not be counted as governed release evidence.

## Use the report catalog

Open the Test Automation report explorer to run available governed reports. Reports can cover execution outcomes, performance, dataset iterations, migrations, coverage, evidence, schedules, providers, frameworks, and failure diagnostics.

Before sharing a report:

1. Confirm its organization and team filters.
2. Check the time range and release scope.
3. Distinguish proposed mappings from approved traceability.
4. Confirm that missing evidence is not being interpreted as a passing result.
5. Drill into the underlying runs and artifacts for material conclusions.

## Create and manage a test-automation dashboard

Authorized users can create test-automation dashboards and add suitable catalog
results or saved metrics for different audiences.

1. Open `Test Automation`, then open dashboard management.
2. Select `Create dashboard` and use a name that identifies the audience or review.
3. Add reports from the governed report catalog or add approved saved metrics.
4. Arrange the dashboard so summary posture appears before diagnostic detail.
5. Save and verify the organization, team, application, release, environment, and
   time filters.
6. Rename the dashboard when its purpose changes, rather than creating an ambiguous
   duplicate.
7. Before deleting a dashboard, confirm that another operating review or shared link
   does not depend on it. Deleting the dashboard does not delete source test runs.

Catalog availability depends on your role and the evidence available to the selected
organization. A report missing from the catalog is not evidence that the underlying
quality condition passed.

## Review external-resource intelligence

1. Select `External Resources` in LoopIQ Analytics.
2. Review total, active, and stale resources and the number of connections.
3. Compare `Resources by product` and the `Resource catalog`.
4. Review `Mapping governance` for proposed, approved, and rejected links.
5. Inspect the `External-resource event pipeline` for recent product events.

Stale resources need investigation; they do not prove that the provider currently has no risk or activity.

## Review OpenText intelligence

When an organization has synchronized OpenText data, the external-resource page adds:

* record, product, severity, staleness, and latest-sync indicators
* `OpenText evidence by domain`
* `Governed release mappings`
* `OpenText 30-day signal trend`
* `Helix and agent release signals`

Use the provider record and approved release mapping to validate a material finding before using it in a Release Compliance Dossier.

## Troubleshooting empty or inconsistent analytics

* Confirm that the source platform and Analytics use the same organization membership.
* Check the selected team, application, release, environment, and time range.
* Refresh provider synchronization and review resource freshness.
* Confirm that test runs are governed rather than hidden diagnostic dry runs.
* Check whether a mapping is only proposed.
* Open the underlying record before assuming zero means no risk.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.