unittest_toolchain

ATTRIBUTES

NameDescriptionTypeMandatoryDefault
nameA unique name for this target.Namerequired
failure_templ-Stringrequired
file_ext-Stringrequired
join_on-Stringrequired
success_templ-Stringrequired

analysistest.make

Creates an analysis test rule from its implementation function.

An analysis test verifies the behavior of a “real” rule target by examining and asserting on the providers given by the real target.

Each analysis test is defined in an implementation function that must then be associated with a rule so that a target can be built. This function handles the boilerplate to create and return a test rule and captures the implementation function's name so that it can be printed in test feedback.

An example of an analysis test:

def _your_test(ctx):
  env = analysistest.begin(ctx)

  # Assert statements go here

  return analysistest.end(env)

your_test = analysistest.make(_your_test)

Recall that names of test rules must end in _test.

PARAMETERS

NameDescriptionDefault Value
implThe implementation function of the unit test.none
expect_failureIf true, the analysis test will expect the target_under_test to fail. Assertions can be made on the underlying failure using asserts.expect_failureFalse
attrsAn optional dictionary to supplement the attrs passed to the unit test's rule() constructor.{}
fragmentsAn optional list of fragment names that can be used to give rules access to language-specific parts of configuration.[]
config_settingsA dictionary of configuration settings to change for the target under test and its dependencies. This may be used to essentially change ‘build flags’ for the target under test, and may thus be utilized to test multiple targets with different flags in a single build{}

analysistest.begin

Begins a unit test.

This should be the first function called in a unit test implementation function. It initializes a “test environment” that is used to collect assertion failures so that they can be reported and logged at the end of the test.

PARAMETERS

NameDescriptionDefault Value
ctxThe Starlark context. Pass the implementation function's ctx argument in verbatim.none

analysistest.end

Ends an analysis test and logs the results.

This must be called and returned at the end of an analysis test implementation function so that the results are reported.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by analysistest.begin.none

analysistest.fail

Unconditionally causes the current test to fail.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
msgThe message to log describing the failure.none

analysistest.target_actions

Returns a list of actions registered by the target under test.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by analysistest.begin.none

analysistest.target_bin_dir_path

Returns ctx.bin_dir.path for the target under test.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by analysistest.begin.none

analysistest.target_under_test

Returns the target under test.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by analysistest.begin.none

asserts.expect_failure

Asserts that the target under test has failed with a given error message.

This requires that the analysis test is created with analysistest.make() and expect_failures = True is specified.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by analysistest.begin.none
expected_failure_msgThe error message to expect as a result of analysis failures.""

asserts.equals

Asserts that the given expected and actual values are equal.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
expectedThe expected value of some computation.none
actualThe actual value returned by some computation.none
msgAn optional message that will be printed that describes the failure. If omitted, a default will be used.None

asserts.false

Asserts that the given condition is false.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
conditionA value that will be evaluated in a Boolean context.none
msgAn optional message that will be printed that describes the failure. If omitted, a default will be used.“Expected condition to be false, but was true.”

asserts.set_equals

Asserts that the given expected and actual sets are equal.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
expectedThe expected set resulting from some computation.none
actualThe actual set returned by some computation.none
msgAn optional message that will be printed that describes the failure. If omitted, a default will be used.None

asserts.new_set_equals

Asserts that the given expected and actual sets are equal.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
expectedThe expected set resulting from some computation.none
actualThe actual set returned by some computation.none
msgAn optional message that will be printed that describes the failure. If omitted, a default will be used.None

asserts.true

Asserts that the given condition is true.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
conditionA value that will be evaluated in a Boolean context.none
msgAn optional message that will be printed that describes the failure. If omitted, a default will be used.“Expected condition to be true, but was false.”

register_unittest_toolchains

Registers the toolchains for unittest users.

PARAMETERS

unittest.make

Creates a unit test rule from its implementation function.

Each unit test is defined in an implementation function that must then be associated with a rule so that a target can be built. This function handles the boilerplate to create and return a test rule and captures the implementation function's name so that it can be printed in test feedback.

The optional attrs argument can be used to define dependencies for this test, in order to form unit tests of rules.

An example of a unit test:

def _your_test(ctx):
  env = unittest.begin(ctx)

  # Assert statements go here

  return unittest.end(env)

your_test = unittest.make(_your_test)

Recall that names of test rules must end in _test.

PARAMETERS

NameDescriptionDefault Value
implThe implementation function of the unit test.none
attrsAn optional dictionary to supplement the attrs passed to the unit test's rule() constructor.{}

unittest.suite

Defines a test_suite target that contains multiple tests.

After defining your test rules in a .bzl file, you need to create targets from those rules so that blaze test can execute them. Doing this manually in a BUILD file would consist of listing each test in your load statement and then creating each target one by one. To reduce duplication, we recommend writing a macro in your .bzl file to instantiate all targets, and calling that macro from your BUILD file so you only have to load one symbol.

You can use this function to create the targets and wrap them in a single test_suite target. If a test rule requires no arguments, you can simply list it as an argument. If you wish to supply attributes explicitly, you can do so using partial.make(). For instance, in your .bzl file, you could write:

def your_test_suite():
  unittest.suite(
      "your_test_suite",
      your_test,
      your_other_test,
      partial.make(yet_another_test, timeout = "short"),
  )

Then, in your BUILD file, simply load the macro and invoke it to have all of the targets created:

load("//path/to/your/package:tests.bzl", "your_test_suite")
your_test_suite()

If you pass N unit test rules to unittest.suite, N + 1 targets will be created: a test_suite target named ${name} (where ${name} is the name argument passed in here) and targets named ${name}_test_${i}, where ${i} is the index of the test in the test_rules list, which is used to uniquely name each target.

PARAMETERS

NameDescriptionDefault Value
nameThe name of the test_suite target, and the prefix of all the test target names.none
test_rulesA list of test rules defines by unittest.test.none

unittest.begin

Begins a unit test.

This should be the first function called in a unit test implementation function. It initializes a “test environment” that is used to collect assertion failures so that they can be reported and logged at the end of the test.

PARAMETERS

NameDescriptionDefault Value
ctxThe Starlark context. Pass the implementation function's ctx argument in verbatim.none

unittest.end

Ends a unit test and logs the results.

This must be called and returned at the end of a unit test implementation function so that the results are reported.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none

unittest.fail

Unconditionally causes the current test to fail.

PARAMETERS

NameDescriptionDefault Value
envThe test environment returned by unittest.begin.none
msgThe message to log describing the failure.none