Using google test in Bazel project

I'm using Bazel for my repository of computer vision samples. Currently, I work on image projection example and want to add tests. One of the best options for the unit test frameworks is the google test.

Bazel has a rich functionality to use external libraries in the project. The external library can be used a from local folder, http archive and git repository.

To be used as dependency in Bazel the library should be a bazel project. So erther it should already contain BUILD file, or we should provide the BUILD file in the dependent project.

Most of the examples of google test usage reference the second option: they propose to add "new_git_repository" the Bazel WORKSPACE and provide manually written BUILD file.

Obviously it is not the best solution since I would have to maintain the build rules for an external project.

But luckily in the release 1.8.1 the google test prject support Bazel build as well. And can be added to workspace as easy as
# WORKSPACE
load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository")
# ...
git_repository(
    name = "googletest",
    remote = "https://github.com/google/googletest.git",
    tag = "release-1.8.1"
)
 And later in your project it can be used like:
# BUILD
cc_test(
    name = "test_example",
    srcs = [
        "test_example.cpp"
    ],
    deps = [
        "@googletest//:gtest",
        "@googletest//:gtest_main"
    ]
)
"gtest_main" in my example above is used to avoid implementing own main function for test.

Tests themself can be written as usually, the smallest example:
#include <gmock/gmock.h>

TEST(TestExample, test)
{
    ASSERT_TRUE(true);
}
And now run:
$ bazel test ...
...
//gtest_example:test_example                                             PASSED in 0.1s

Executed 1 out of 1 test: 1 test passes.
INFO: Build completed successfully, 26 total actions
The examples are available on github:
WORKSPACE
BUILD

Comments

  1. gallaeagleburgerJune 19, 2022 at 4:28 AM

    King Casino Login | Full Analysis (2021) - Macmerit
    Login King Casino to make a deposit 메리트카지노 of between $1 and $2,000. The 파라오카지노 King casino gives access to new players using its own

    ReplyDelete
  2. cacyigarashiNovember 9, 2022 at 11:46 AM

    Harrah’s pioneered the now trade standard Total Rewards participant monitoring system, first with a punchcard program launched in 1985, then with a digital program and magnetic cards in the Nineteen Nineties. Slots were easy to track, and stood on the very center of the program. The system grew even more refined underneath the auspices of former CEO Gary Loveman. Loveman arrived at Harrah’s fresh from teaching at Harvard Business School, and he introduced a methodical enterprise savvy to an trade that, in some ways, had spent a long time winging it. Slot machines are available on a first-come, first-served foundation and must be consistently 1xbet performed.

    ReplyDelete

Post a Comment

Popular posts from this blog

Compilation from macOS(Intel) to linux x86_64 finaly works. Cross compilation of the rust code with bazel. Part 2.

This is the continuation of cross-compilation  topic that I've started in previous part What? Do I really need to configure C++ compiler to compile rust? Cross compilation of the rust code with bazel. Part 1. Since we need to add C++ cross-compilation toolchain, let's add the pure C++ project. This will help us to test the C++ toolchain separately I've added a typical C++ hello world impliemntaion and a BUILD file for it: cc_binary ( name = "hello-world" , srcs = [ "main.cpp" ], ) And our goal is to make it compilable for linux by command: bazel build //cpp/hello_world:hello-world --platforms=//:x86_64-linux --incompatible_enable_cc_toolchain_resolution If we just try it, we get and error,  (23:01:17) ERROR: /private/var/tmp/_bazel_evgenypetrov/e83d964deb47c21842622d1b7ffa55fc/external/bazel_tools/tools/cpp/BUILD:58:19: in cc_toolchain_alias rule @baze l_tools//tools/cpp:current_cc_toolchain: Unable to find a CC toolchain using toolchain resolution. ...
Read more

Fetching toolchains at build time. Cross compilation of the rust code with bazel. Part 4

Adding toolchain binaries directly int the repository isn't actually a good idea: the repository is getting bigger and bigger. It takes a while to check it out even in a the case, you want just to take a look. So to add new toolchain, we will try to fetch it on "runtime", i.e. when we execute some bazel command. Today we will add a toolchain, that compiles aarch64 binaries from macOS. For fetching something from internet, bazel has an "http_archive" rule, we have already used it to fetch the rust_rules in the Part 1. We can fetch arbitrary archives with this rule, in our case the toolchain tarball. http_archive ( name = "aarch64-unknown-linux-musl" , sha256 = "4fbe95500c327828b437f380bb15851e9a8126cf95180fbf15b76b78e0322ae3" , urls = [ "https://github.com/messense/homebrew-macos-cross-toolchains/releases/download/v11.2.0-1/aarch64-unknown-linux-musl-x86_64-darwin.tar.gz" ], strip_prefix = "aarch64-unknown-linux-...
Read more

Cross compilation for ARM v7. Cross compilation of the rust code with bazel. Part 3.

This is the third part of the series "Cross compilation of rust with bazel". Previous topics: What? Do I really need to configure C++ compiler to compile rust? Cross compilation of the rust code with bazel. Part 1. Compilation from macOS(Intel) to linux x86_64 finaly works. Cross compilation of the rust code with bazel. Part 2.   Next challenge is to cross-compile for armv7. This part we did together with my colleague Dima and we did it on linux. First thing, that we need is to add the target platform into our root BUILD.bazel platform ( name = "armv7-linux-musleabihf" , constraint_values = [ "@platforms//cpu:armv7" , "@platforms//os:linux" , ], ) And rust toolchain for the new target in the WORKSPACE file: rust_register_toolchains ( edition = "2021" , extra_target_triples = [ "x86_64-unknown-linux-musl" , "armv7-unknown-linux-musleabihf" , # NEW ], ) And as we remember from the part 1 ,...
Read more