Skip to content

integration/git: use static subtest names in TestFetchRepositoryInfo*#5375

Open
pietern wants to merge 1 commit into
mainfrom
non-dynamic-subtest-name
Open

integration/git: use static subtest names in TestFetchRepositoryInfo*#5375
pietern wants to merge 1 commit into
mainfrom
non-dynamic-subtest-name

Conversation

@pietern
Copy link
Copy Markdown
Contributor

@pietern pietern commented May 29, 2026

The TestFetchRepositoryInfo* tests in integration/libs/git passed runtime values into t.Run — temporary workspace paths containing UUIDs and t.TempDir() paths — so each subtest got a different name on every run. In aggregated test output this shows up as thousands of distinct one-off test names instead of a single stable entry.

This replaces the dynamic names with static ones (subdir, root, non-existent) by giving each table case an explicit name field.

A sweep over every t.Run call in the repository found this to be the only place with this pattern.

This pull request and its description were written by Isaac.

The TestFetchRepositoryInfo* tests passed runtime values into t.Run --
temporary workspace paths containing UUIDs and t.TempDir() paths -- so
each subtest got a different name on every run. In aggregated test
output this shows up as thousands of distinct one-off test names instead
of a single stable entry.

Replace the dynamic names with static ones (subdir, root, non-existent)
by giving each table case an explicit name field.

Co-authored-by: Isaac
@pietern pietern temporarily deployed to test-trigger-is May 29, 2026 12:00 — with GitHub Actions Inactive
@pietern pietern temporarily deployed to test-trigger-is May 29, 2026 12:00 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown
Contributor

Waiting for approval

Based on git history, these people are best suited to review:

  • @simonfaltum -- recent work in integration/libs/git/

Eligible reviewers: @Divyansh-db, @chrisst, @hectorcast-db, @mihaimitrea-db, @parthban-db, @rauchy, @renaudhartert-db, @tanmay-db, @tejaskochar-db

Suggestions based on git history. See OWNERS for ownership rules.

@eng-dev-ecosystem-bot
Copy link
Copy Markdown
Collaborator

Commit: b59957d

Run: 26636030519

@pietern pietern requested a review from andrewnester May 29, 2026 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants