Skip to content

chore(ci-compliance): use public fixture names in the upgrade-map tests - #24

Open
sakanni wants to merge 1 commit into
developfrom
internal-tickets-#43-PublicFixtureNames
Open

sakanni wants to merge 1 commit into
developfrom
internal-tickets-#43-PublicFixtureNames

Conversation

@sakanni

@sakanni sakanni commented Sep 29, 2026

Copy link
Copy Markdown
Collaborator

Issues addressed by this PR

Three fixtures and one comment added in #23 named private repositories. Each is a literal project directory in a repository that is private, so a path search on it returns that repository and nothing else, and this repository is public.

Substituted for BHoM_Datasets, which has the layout the comment describes and is public, and Structure_oM, which is public and already used two lines below in the same block.

Test files

FileFilterTests, 88 passing, unchanged from before the substitution. The assertions keep their shape and count: these paths carry no datasets substring, so they exercise the upgrade-map predicate on its own exactly as before.

Changelog

No behaviour change. Test fixture and comment names only.

Additional comments

The names remain in this repository's history and that cannot be undone. The exposure is stopped going forward rather than erased.

Three fixtures and one comment added in #23 named private repositories: a comment
naming a private repository's upgrade map, and two test cases under a private
repository's oM project directory. Each name is a literal project directory in a
repository that is private, so a path search on it returns that repository alone.

Substituted for BHoM_Datasets, which has the layout the comment describes and is
public, and Structure_oM, which is public and already used two lines below in the
same block. The assertions are unchanged in shape and count: these paths carry no
"datasets" substring, so they exercise the upgrade-map predicate on its own exactly
as before.

88 unit tests and 66 integration tests pass, unchanged from before the substitution.
@sakanni
sakanni marked this pull request as ready for review September 29, 2026 15:32
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.

1 participant