Skip to contentSkip to conversation

kunit: Kconfig: enable a KUNIT_ALL_TESTS fragment

PATCH In review Anders Roxell 2 participants 2 messages May 11, 2020 – May 28, 2020

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH v3 1/6 kunit: Kconfig: enable a KUNIT_ALL_TESTS fragment

Make it easier to enable all KUnit fragments. This is useful for kernel devs or testers, so its easy to get all KUnit tests enabled and if new gets added they will be enabled as well. Fragments that has to be builtin will be missed if CONFIG_KUNIT_ALL_TESTS is set as a module.

---
 lib/kunit/Kconfig | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
lib/kunit/Kconfig +14 -0
index 95d12e3d6d95..bdeee7639005 100644
@@ -41,4 +41,18 @@ config KUNIT_EXAMPLE_TEST
 	  is intended for curious hackers who would like to understand how to
 	  use KUnit for kernel development.
 
+config KUNIT_ALL_TESTS
+	tristate "All KUnit tests with satisfied dependencies"
+	help
+	  Enables all KUnit tests, if they can be enabled.
+	  KUnit tests run during boot and output the results to the debug log
+	  in TAP format (http://testanything.org/). Only useful for kernel devs
+	  running the KUnit test harness, and not intended for inclusion into a
+	  production build.
+
+	  For more information on KUnit and unit tests in general please refer
+	  to the KUnit documentation in Documentation/dev-tools/kunit/.
+
+	  If unsure, say N.
+
 endif # KUNIT
Signature · 1 line
2.20.1
Reviewed-by on v3 1/6
#1 lore raw
Quoted 7 lines · Anders Roxell

Make it easier to enable all KUnit fragments. This is useful for kernel devs or testers, so its easy to get all KUnit tests enabled and if new gets added they will be enabled as well. Fragments that has to be builtin will be missed if CONFIG_KUNIT_ALL_TESTS is set as a module.