Skip to main content

Application

Open Application in the navigation rail to inspect your connected application's code and testing coverage. Its tabs are Commits, Pull requests, and Coverage. Connect the source under Settings → Repositories → Application code.

Use Set up automation, or open Automations → New automation, to configure GitHub workflows and review suggested feature updates. See GitHub workflows.

Older versions called this section App Code or Codebase; existing /codebase links remain supported.

A tour of Application: opening it from the navigation, browsing commits and a changed-file diff with recommended tests, the Pull requests tab, the Coverage file browser with its filters, a file with its Tested by relationships and an @covers: tag, and the structural map beside executed-line coverage.

Changes and pull requests​

On supported repository connections, browse commits by branch, inspect a commit or pull request, and read its changed-file diff. TestVibe can recommend tests related to the changed files. Review the recommendations before running them; a match is a suggested relationship, not proof that the change is fully tested.

Commit and pull-request browsing currently supports GitHub. Other supported source providers can supply code context without offering every change-review action; the page explains unavailable actions.

Coverage​

The Coverage tab combines the file browser and coverage information. Browse folders with breadcrumbs, search across files, and switch between All files, Without tests, and With tests. Select a file to see its Tested by relationships and open the linked tests.

Mappings come from Assistant scanning and explicit @covers: tags on Gherkin scenarios, such as @covers:Services/CheckoutService. Use a path qualifier when a class name is ambiguous; TestVibe leaves ambiguous tags unmapped. Correct a relationship by removing a stale link or mapping a test yourself; manual corrections survive rescans.

Structural and executed coverage​

The structural map relates application areas and files to UI tests. It can reveal files with no mapped test, but a mapping alone does not prove every line ran.

Coverage collection can run a project's .NET or Node.js test command and ingest executed-line coverage. Unsupported stacks can still have a structural map without an executed-line percentage. Inspect the selected branch, snapshot, and collection result before comparing numbers.

Scanning and coverage collection run on demand and can consume credits. A connected source repository does not start a paid scan automatically.