bindings: cxx: add a workaround for --success run

If run with --success, all expressions are evaluated and printed out.
But REQUIRE_FALSE(chip) tries to iterate over the chip resulting in this
backtrace:

[...]

Work around this by forcing catch2 to call gpiod::chip::operator bool().

Signed-off-by: Alexander Stein <alexander.stein@mailbox.org>
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>

diff --git a/bindings/cxx/tests/tests-chip.cpp b/bindings/cxx/tests/tests-chip.cpp
index c9eb8e537c23a561c8e62621cc4f8e892ce05262..1c69872cded6029b3d084c90b7ec7a3c5db8207c 100644 (file)
--- a/bindings/cxx/tests/tests-chip.cpp
+++ b/bindings/cxx/tests/tests-chip.cpp
@@ -70,7 +70,7 @@ TEST_CASE("GPIO chip can be opened with the open() method in different modes", "
        mockup::probe_guard mockup_chips({ 8, 8, 8 });
        ::gpiod::chip chip;
 
-       REQUIRE_FALSE(chip);
+       REQUIRE_FALSE(!!chip);
 
        SECTION("open by name")
        {
@@ -102,7 +102,7 @@ TEST_CASE("Uninitialized GPIO chip behaves correctly", "[chip]")
 
        SECTION("uninitialized chip is 'false'")
        {
-               REQUIRE_FALSE(chip);
+               REQUIRE_FALSE(!!chip);
        }
 
        SECTION("using uninitialized chip throws logic_error")
@@ -149,7 +149,7 @@ TEST_CASE("Chip object can be reset", "[chip]")
        ::gpiod::chip chip(mockup::instance().chip_name(0));
        REQUIRE(chip);
        chip.reset();
-       REQUIRE_FALSE(chip);
+       REQUIRE_FALSE(!!chip);
 }
 
 TEST_CASE("Chip info can be correctly retrieved", "[chip]")