GlossaryTest Discovery

Test Discovery

Test discovery is the automated process of finding, cataloging, and registering existing test definitions across code repositories, frameworks, and infrastructure.

Table of Contents

Table of Contents

Further Reading

No items found.
No items found.
No items found.
No items found.
No items found.
No items found.

How test discovery works

  1. Connect repositories, clusters, or test frameworks.
  2. Scan for test files, manifests, or definitions using naming rules or patterns.
  3. Register each test with metadata such as framework, owner, and location.
  4. Watch for changes and update the catalog automatically.
  5. Show every discovered test in one place for running and reporting.

Types of test discovery

  • Framework discovery: runners like pytest or JUnit find tests by naming patterns
  • Repository discovery: scanning Git for test files and manifests
  • Cluster discovery: finding tests already defined in Kubernetes
  • Impact-based discovery: finding tests related to changed code

Manual cataloging vs. automated discovery

Manual lists fall out of date quickly. Automated discovery keeps pace with the code.

Manual cataloging Automated discovery
Freshness Stale within weeks Always current
Effort High, ongoing Low after setup
Coverage gaps Common Easy to spot
Duplicates Hard to find Visible in one catalog

Why test discovery matters

As coverage grows across teams, frameworks, and repositories, tracking tests by hand stops working.

  • Automatic registration: new or changed tests are picked up right away
  • Full visibility: every test asset across environments in one view
  • Less duplication: teams see what already exists before writing more
  • Aligned coverage: the catalog keeps up with the codebase

Consider a SaaS company with 15 teams and dozens of repositories. Discovery shows three teams wrote nearly identical login tests. They consolidate and save maintenance time.

Common challenges with test discovery

  • Inconsistent naming: tests that do not follow conventions get missed
  • Many frameworks: each tool stores tests differently
  • Stale entries: deleted tests linger in the catalog
  • Ownership: unclear who owns each discovered test

How test discovery relates to Testkube

Testkube can discover tests from Git repositories and Kubernetes clusters and manage them centrally.

  • Git scanning: find test manifests in connected repositories
  • Cluster discovery: detect tests already defined in Kubernetes
  • Multi-framework: Cypress, Postman, k6, Playwright, and more through standard definitions
  • Version-aware: registrations follow changes in Git
  • Central view: every discovered test in the Testkube dashboard

Frequently Asked Questions (FAQs)

What is test discovery?

It is the automated process of finding and cataloging existing tests.

How do test frameworks discover tests?

Most use naming patterns, such as files or functions that start with test.

Why does test discovery matter for large teams?

It prevents duplicate work and shows coverage gaps across many repositories.

Can Testkube discover tests in Git?

Yes. Testkube can find test definitions in connected Git repositories.

What is the difference between test discovery and test impact analysis?

Discovery finds all tests. Impact analysis picks the tests affected by a specific change.

How do I keep discovered tests up to date?

Connect discovery to version control so changes update the catalog automatically.

Related Terms and Concepts

No items found.