Skip to content

Conversation

rickeylev
Copy link
Collaborator

tests: move various supporting code under tests/support

  • Move subject classes under support
  • Switch to using rules_testing DefaultInfo subject
  • Move fake cc toolchains under tests/support/cc_toolchains (these
    are used in several places, not just tests/cc)
  • Make literal references of old //tests/cc locations use the
    constants from support.bzl

This is both for code clarity (support code being in a common location),
but also to make it easier to import the support code for the subset
of tests Google imports and runs.

* Move subject classes under support
* Switch to using rules_testing DefaultInfo subject
* Move fake cc toolchains under tests/support/cc_toolchains (these
  are used in several places, not just tests/cc)
* Make literal references of old //tests/cc locations use the
  constants from support.bzl

This is both for code clarity (support code being in a common location),
but also to make it easier to import the support code for the subset
of tests Google imports and runs.
@rickeylev rickeylev requested a review from oprypin September 4, 2024 22:36
@rickeylev rickeylev requested a review from aignas as a code owner September 4, 2024 22:36
@rickeylev rickeylev added this pull request to the merge queue Sep 5, 2024
Merged via the queue into bazel-contrib:main with commit 612baef Sep 5, 2024
4 checks passed
@rickeylev rickeylev deleted the refactor.mv.test.cc.toolchains branch September 5, 2024 23:52
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