Kconfig 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. #
  2. # KUnit base configuration
  3. #
  4. menuconfig KUNIT
  5. tristate "KUnit - Enable support for unit tests"
  6. select GLOB if KUNIT=y
  7. select HAS_IOMEM
  8. help
  9. Enables support for kernel unit tests (KUnit), a lightweight unit
  10. testing and mocking framework for the Linux kernel. These tests are
  11. able to be run locally on a developer's workstation without a VM or
  12. special hardware when using UML. Can also be used on most other
  13. architectures. For more information, please see
  14. Documentation/dev-tools/kunit/.
  15. if KUNIT
  16. config KUNIT_DEBUGFS
  17. bool "KUnit - Enable /sys/kernel/debug/kunit debugfs representation" if !KUNIT_ALL_TESTS
  18. default KUNIT_ALL_TESTS
  19. help
  20. Enable debugfs representation for kunit. Currently this consists
  21. of /sys/kernel/debug/kunit/<test_suite>/results files for each
  22. test suite, which allow users to see results of the last test suite
  23. run that occurred.
  24. config KUNIT_TEST
  25. tristate "KUnit test for KUnit" if !KUNIT_ALL_TESTS
  26. default KUNIT_ALL_TESTS
  27. help
  28. Enables the unit tests for the KUnit test framework. These tests test
  29. the KUnit test framework itself; the tests are both written using
  30. KUnit and test KUnit. This option should only be enabled for testing
  31. purposes by developers interested in testing that KUnit works as
  32. expected.
  33. config KUNIT_EXAMPLE_TEST
  34. tristate "Example test for KUnit" if !KUNIT_ALL_TESTS
  35. default KUNIT_ALL_TESTS
  36. help
  37. Enables an example unit test that illustrates some of the basic
  38. features of KUnit. This test only exists to help new users understand
  39. what KUnit is and how it is used. Please refer to the example test
  40. itself, lib/kunit/example-test.c, for more information. This option
  41. is intended for curious hackers who would like to understand how to
  42. use KUnit for kernel development.
  43. config KUNIT_ALL_TESTS
  44. tristate "All KUnit tests with satisfied dependencies"
  45. help
  46. Enables all KUnit tests, if they can be enabled.
  47. KUnit tests run during boot and output the results to the debug log
  48. in TAP format (http://testanything.org/). Only useful for kernel devs
  49. running the KUnit test harness, and not intended for inclusion into a
  50. production build.
  51. For more information on KUnit and unit tests in general please refer
  52. to the KUnit documentation in Documentation/dev-tools/kunit/.
  53. If unsure, say N.
  54. config KUNIT_DEFAULT_ENABLED
  55. bool "Default value of kunit.enable"
  56. default y
  57. help
  58. Sets the default value of kunit.enable. If set to N then KUnit
  59. tests will not execute unless kunit.enable=1 is passed to the
  60. kernel command line.
  61. In most cases this should be left as Y. Only if additional opt-in
  62. behavior is needed should this be set to N.
  63. config KUNIT_MANAGER
  64. tristate "Manager for KUnit"
  65. depends on SEC_KUNIT
  66. depends on !UML
  67. default m
  68. help
  69. Enables KUnit Manager. KUnit Manager is a sysfs node for triggering
  70. on-device testing in Samsung kernel.
  71. config SEC_KUNIT
  72. bool "Enable support for unit tests (KUnit)"
  73. help
  74. Deprecated: CONFIG_SEC_KUNIT does not be used anymore. Please use
  75. CONFIG_KUNIT. This is only for previous tests built by SEC_KUNIT.
  76. endif # KUNIT