[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201012222050.999431-7-dlatypov@google.com>
Date: Mon, 12 Oct 2020 15:20:44 -0700
From: Daniel Latypov <dlatypov@...gle.com>
To: dlatypov@...gle.com
Cc: alan.maguire@...cle.com, brendanhiggins@...gle.com,
davidgow@...gle.com, keescook@...omium.org,
kunit-dev@...glegroups.com, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, mcgrof@...nel.org,
sboyd@...nel.org, skhan@...uxfoundation.org
Subject: [RFC v2 06/12] kunit: expose kunit_set_failure() for use by mocking
Being able to fail the test outside of expectations and assertions is a
requirement for new features, e.g. mocking, dynamic analysis, etc.
Signed-off-by: Daniel Latypov <dlatypov@...gle.com>
---
include/kunit/test.h | 2 ++
lib/kunit/test.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/kunit/test.h b/include/kunit/test.h
index 0eb3abb00da4..05330593243d 100644
--- a/include/kunit/test.h
+++ b/include/kunit/test.h
@@ -233,6 +233,8 @@ struct kunit {
void kunit_init_test(struct kunit *test, const char *name, char *log);
+void kunit_set_failure(struct kunit *test);
+
int kunit_run_tests(struct kunit_suite *suite);
size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
diff --git a/lib/kunit/test.c b/lib/kunit/test.c
index 4e8c74c89073..1ccf6dbecd73 100644
--- a/lib/kunit/test.c
+++ b/lib/kunit/test.c
@@ -15,7 +15,7 @@
#include "debugfs.h"
#include "try-catch-impl.h"
-static void kunit_set_failure(struct kunit *test)
+void kunit_set_failure(struct kunit *test)
{
WRITE_ONCE(test->success, false);
}
--
2.28.0.1011.ga647a8990f-goog
Powered by blists - more mailing lists