Bump rules_testing from 0.7.0 to 0.9.0

[dependabot]

Bumps rules_testing from 0.7.0 to 0.9.0.

Release notes

Sourced from rules_testing's releases.

v0.9.0

WORKSPACE snippet:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_testing",
    sha256 = "281b69eed71e2b95cefc284ee5a1a9f7c5088141b58f2508be910eb22f13b986",
    strip_prefix = "rules_testing-0.9.0",
    url = "https://github.com/bazelbuild/rules_testing/releases/download/v0.9.0/rules_testing-v0.9.0.tar.gz",
)

What's Changed

Other Changes

• Accept a provider_name in TargetSubject.provider() and TargetSubject.has_provider() by @​copybara-service[bot] in bazelbuild/rules_testing#137
• Add an StrSubject for basename to FileSubject by @​copybara-service[bot] in bazelbuild/rules_testing#138

Full Changelog: bazelbuild/rules_testing@v0.8.0...v0.9.0

v0.8.0

WORKSPACE snippet:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_testing",
    sha256 = "89feaf18d6e2fc07ed7e34510058fc8d48e45e6d2ff8a817a718e8c8e4bcda0e",
    strip_prefix = "rules_testing-0.8.0",
    url = "https://github.com/bazelbuild/rules_testing/releases/download/v0.8.0/rules_testing-v0.8.0.tar.gz",
)

What's Changed

Other Changes

• chore(deps): stardoc, rules_python, rules_cc, protobuf, rule_java by @​rickeylev in bazelbuild/rules_testing#117
• chore: remove defunct file and todo by @​copybara-service in bazelbuild/rules_testing#118
• chore: upgrade CI from Bazel 5 to 6 by @​comius in bazelbuild/rules_testing#122
• Copy unittest.bzl tests from bazel_skylib to rules_testing. by @​copybara-service in bazelbuild/rules_testing#123
• Internal functionality by @​copybara-service in bazelbuild/rules_testing#124
• chore: Prepare WORKSPACE mode for Bazel 8 by @​hvadehra in bazelbuild/rules_testing#127
• Internal change by @​copybara-service in bazelbuild/rules_testing#129
• Add bindir to formatting variables by @​copybara-service in bazelbuild/rules_testing#131
• Remove collect_actions_recursively by @​copybara-service in bazelbuild/rules_testing#133
• Support testing aspects by @​copybara-service in bazelbuild/rules_testing#135

... (truncated)

Changelog

Sourced from rules_testing's changelog.

rules_testing Changelog

Unreleased

Changed

• TargetSubject.provider() and TargetSubject.has_provider() accept a provider_name for better error messaging.
• Added FileSubject.basename() and FileSubject.actual
• The testing_aspect is applied to util.force_exec_config's tools attribute allowing tests to assert on it like a regular target-under-test
• Added ActionSubject.meta, exposing the subject's ExpectMeta object.
• Added CollectionSubject.contains_no_duplicates() assertion.
• Added DepsetFileSubject.contains_none_of() assertion.

Added

• Nothing yet

0.8.0 - 2025-03-17

Changed

• Add {bindir} to formatting variables.
• Format values in ActionsSubject.contains_flag_values().
• CollectionSubject accepts new constructor parameter format. When used all asserts are formatted.
• Actionsubjects.argv() formats all asserts, for example action.argv().contains_at_least(["-f", "{bindir}/{package}/input.txt"]).

Added

• Added support for testing actions created in an aspect, via util.make_testing_aspect and analysis_test's testing_aspect parameter.

Removed

• Removed util.recursive_testing_aspect and analysis_test.collect_actions_recursively. They were never properly implemented.

Commits

• db007bf Add an StrSubject for basename to FileSubject
• 3909cc0 Accept a provider_name in TargetSubject.provider() and `TargetSubject.has...
• 52a6567 Update changelog for 0.8.0 release
• c131725 Support testing aspects
• 7d6ad05 Remove collect_actions_recursively
• d150114 Implement collection subjects that apply formatting
• c786da4 Add bindir to formatting variables
• 6c33817 Internal change
• 1358636 Merge pull request #127 from hvadehra:master
• a6cd92e chore: Prepare WORKSPACE mode for Bazel 8
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)