bazel
/
bazel-skylib
mirror of https://github.com/bazelbuild/bazel-skylib
2
0
Fork 0
Code Issues Releases Activity
bazel-skylib/tests/BUILD

96 lines
2.1 KiB
Python
Raw Normal View History

Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
load("//:bzl_library.bzl", "bzl_library")
Add a build_test rule. (#97) * Add a build_test rule. This rules (marco) provides a 'test' target that can be used to ensure other targets build.
2019-01-25 19:34:15 +00:00
load(":build_test_tests.bzl", "build_test_test_suite")
Initial check-in.
2017-10-10 14:59:31 +00:00
load(":collections_tests.bzl", "collections_test_suite")
load(":dicts_tests.bzl", "dicts_test_suite")
maprule: an improved version of genrule() (#86) maprule() is an improved version of native.genrule(), with the following advantages: - Maprule can process source files in parallel, creating separate actions for each of them. - Maprule does not require declaring all output files. Instead you declare templates for the output files yielded for each source. Therefore N source files and M templates yield N*M outputs. - Maprule supports both Bash and cmd.exe syntax for its commands via the specialized rules bash_maprule and cmd_maprule. - Maprule's cmd attribute does deliberately not support $(location) expression nor Make Variables, in order to avoid issues and challenges with quoting. (In case of cmd.exe passing empty arguments is impossible). These paths can be passed as envvars instead. - Maprule's add_env attribute does support $(location) expressions (and some extra placeholders) and is the idiomatic way to pass execpaths of labels in "tools" or "srcs" (the shared sources available for all actions) to the command. See https://github.com/bazelbuild/bazel/issues/4319
2019-01-08 08:04:53 +00:00
load(":maprule_tests.bzl", "maprule_test_suite")
update and rename test suites
2019-05-28 21:25:09 +00:00
load(":old_sets_tests.bzl", "old_sets_test_suite")
Fix up lint issues. (#77) Fixed via `buildifier --lint=fix` with buildifier 0.19.2.1
2018-11-26 22:31:29 +00:00
load(":new_sets_tests.bzl", "new_sets_test_suite")
Add support for 'functools.partial' like functionality. (#34) * Add support for 'functools.partial' like functionality. https://docs.python.org/3/library/functools.html#functools.partial
2018-04-17 16:33:38 +00:00
load(":partial_tests.bzl", "partial_test_suite")
Initial check-in.
2017-10-10 14:59:31 +00:00
load(":paths_tests.bzl", "paths_test_suite")
load(":selects_tests.bzl", "selects_test_suite")
Windows: fix tests for native test wrapper (#129) All tests work with `--incompatible_windows_native_test_wrapper` except for the ones already broken on Windows (//tests:analysis_test_e2e_test and //tests:unittest_e2e_test). See https://github.com/bazelbuild/bazel/issues/6622
2019-03-26 09:52:27 +00:00
load(":shell_tests.bzl", "shell_args_test_gen", "shell_test_suite")
Initial check-in.
2017-10-10 14:59:31 +00:00
load(":structs_tests.bzl", "structs_test_suite")
Add type checking functions. Even though it's not great to use type checks, they are frequently useful for checking input types of macros. Because there is no standard way of checking types, at least 2 types of checks are used: - `type(foo) == type([])` - `type(foo) == "list"` The first option is not very readable and the second option seem to be relying on an Bazel implementation detail. Encapsulating type checks into this library enables consistent and easy to understand type checking without explicitly relying on implementation details.
2018-05-08 22:13:31 +00:00
load(":types_tests.bzl", "types_test_suite")
Add analysis-test test framework (#110) This framework allows for easy creation of unittest-like tests to make assertions on the provider-values returned by real targets.
2019-02-14 21:54:42 +00:00
load(":unittest_tests.bzl", "unittest_passing_tests_suite")
Added a lib for version checking and comparison (#13)
2018-01-12 17:18:55 +00:00
load(":versions_tests.bzl", "versions_test_suite")
Initial check-in.
2017-10-10 14:59:31 +00:00
licenses(["notice"])
copy_file: add rule and tests (#123) This PR adds two new rules: copy_file and copy_xfile. Both rules solve a common problem: to copy one file to another location. The problem is routinely solved using a genrule. That however requires Bash, since genrules execute Bash commands. Requiring Bash is a problem on Windows. The new rules do not require Bash on Windows (only on other platforms). The only difference between the rules is that copy_xfile creates an executable file while copy_file doesn't. See https://github.com/bazelbuild/bazel/issues/4319
2019-03-18 12:23:15 +00:00
exports_files(
["unittest.bash"],
visibility = ["//tests:__subpackages__"],
)
Add a build_test rule. (#97) * Add a build_test rule. This rules (marco) provides a 'test' target that can be used to ensure other targets build.
2019-01-25 19:34:15 +00:00
build_test_test_suite()
Initial check-in.
2017-10-10 14:59:31 +00:00
collections_test_suite()
dicts_test_suite()
maprule: an improved version of genrule() (#86) maprule() is an improved version of native.genrule(), with the following advantages: - Maprule can process source files in parallel, creating separate actions for each of them. - Maprule does not require declaring all output files. Instead you declare templates for the output files yielded for each source. Therefore N source files and M templates yield N*M outputs. - Maprule supports both Bash and cmd.exe syntax for its commands via the specialized rules bash_maprule and cmd_maprule. - Maprule's cmd attribute does deliberately not support $(location) expression nor Make Variables, in order to avoid issues and challenges with quoting. (In case of cmd.exe passing empty arguments is impossible). These paths can be passed as envvars instead. - Maprule's add_env attribute does support $(location) expressions (and some extra placeholders) and is the idiomatic way to pass execpaths of labels in "tools" or "srcs" (the shared sources available for all actions) to the command. See https://github.com/bazelbuild/bazel/issues/4319
2019-01-08 08:04:53 +00:00
maprule_test_suite()
update and rename test suites
2019-05-28 21:25:09 +00:00
old_sets_test_suite()
new_sets_test_suite()
Add support for 'functools.partial' like functionality. (#34) * Add support for 'functools.partial' like functionality. https://docs.python.org/3/library/functools.html#functools.partial
2018-04-17 16:33:38 +00:00
partial_test_suite()
Initial check-in.
2017-10-10 14:59:31 +00:00
paths_test_suite()
selects_test_suite()
shell_test_suite()
structs_test_suite()
Added a lib for version checking and comparison (#13)
2018-01-12 17:18:55 +00:00
Add type checking functions. Even though it's not great to use type checks, they are frequently useful for checking input types of macros. Because there is no standard way of checking types, at least 2 types of checks are used: - `type(foo) == type([])` - `type(foo) == "list"` The first option is not very readable and the second option seem to be relying on an Bazel implementation detail. Encapsulating type checks into this library enables consistent and easy to understand type checking without explicitly relying on implementation details.
2018-05-08 22:13:31 +00:00
types_test_suite()
Add analysis-test test framework (#110) This framework allows for easy creation of unittest-like tests to make assertions on the provider-values returned by real targets.
2019-02-14 21:54:42 +00:00
unittest_passing_tests_suite()
Added a lib for version checking and comparison (#13)
2018-01-12 17:18:55 +00:00
versions_test_suite()
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
bzl_library(
Add analysis-test test framework (#110) This framework allows for easy creation of unittest-like tests to make assertions on the provider-values returned by real targets.
2019-02-14 21:54:42 +00:00
name = "unittest_tests_bzl",
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
srcs = ["unittest_tests.bzl"],
Add analysis-test test framework (#110) This framework allows for easy creation of unittest-like tests to make assertions on the provider-values returned by real targets.
2019-02-14 21:54:42 +00:00
visibility = ["//visibility:private"],
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
deps = ["//lib:unittest"],
)
sh_test(
name = "unittest_e2e_test",
srcs = ["unittest_test.sh"],
data = [
":unittest.bash",
Add analysis-test test framework (#110) This framework allows for easy creation of unittest-like tests to make assertions on the provider-values returned by real targets.
2019-02-14 21:54:42 +00:00
":unittest_tests_bzl",
e2e tests: make them run on Windows (#121)
2019-03-19 12:37:33 +00:00
"//lib:dicts.bzl",
"//lib:new_sets.bzl",
"//lib:old_sets.bzl",
"//lib:sets.bzl",
"//lib:types.bzl",
"//lib:unittest.bzl",
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
"//toolchains/unittest:test_deps",
"@bazel_tools//tools/bash/runfiles",
],
tags = ["local"],
)
Add analysis_test rule Targets of this rule verify that targets can be analyzed successfully. This is similar to build_test, except no actual action execution of the underlying targets occur. analysis_test essentially verifies that `bazel build [targets] --nobuild` passes.
2019-02-19 20:16:36 +00:00
sh_test(
name = "analysis_test_e2e_test",
srcs = ["analysis_test_test.sh"],
data = [
":unittest.bash",
"//rules:analysis_test.bzl",
"@bazel_tools//tools/bash/runfiles",
],
tags = ["local"],
)
Windows: fix tests for native test wrapper (#129) All tests work with `--incompatible_windows_native_test_wrapper` except for the ones already broken on Windows (//tests:analysis_test_e2e_test and //tests:unittest_e2e_test). See https://github.com/bazelbuild/bazel/issues/6622
2019-03-26 09:52:27 +00:00
shell_args_test_gen(
name = "shell_spawn_e2e_test_src",
)
sh_test(
name = "shell_spawn_e2e_test",
srcs = [":shell_spawn_e2e_test_src"],
)