From 01040bb9bf6dc5fc83d84a14daed034bd0a67974 Mon Sep 17 00:00:00 2001 From: Niklas Hauser Date: Mon, 29 Feb 2016 15:21:17 +0100 Subject: [PATCH] Do not report failure with uninitialized harness. Calling `raise_failure` before harness is initialized can print unintentional failure strings. This disallows using Unity macros outside of the utest harness. --- "frameworks\\utest/source/harness.cpp" | 4 ++++ 1 file changed, 4 insertions(+) diff --git "a/frameworks\\utest/source/harness.cpp" "b/frameworks\\utest/source/harness.cpp" index a41a980af0..fe5daa23e7 100644 --- "a/frameworks\\utest/source/harness.cpp" +++ "b/frameworks\\utest/source/harness.cpp" @@ -99,6 +99,10 @@ bool Harness::run(const Specification& specification, std::size_t start_case) void Harness::raise_failure(const failure_reason_t reason) { + // ignore a failure, if the Harness has not been initialized. + // this allows using unity assertion macros without setting up utest. + if (test_cases == NULL) return; + status_t fail_status = STATUS_ABORT; { mbed::util::CriticalSectionLock lock;