libubox/tests/cram/test_runqueue.t

check that runqueue is producing expected results:

  $ [ -n "$TEST_BIN_DIR" ] && export PATH="$TEST_BIN_DIR:$PATH"
  $ valgrind --quiet --leak-check=full test-runqueue
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  All done!

  $ test-runqueue-san
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  [1/1] start 'sleep 1'
  [1/1] cancel 'sleep 1'
  [0/1] finish 'sleep 1'
  All done!
add cram based unit tests For improved QA etc. For the start with initial test cases for avl, base64, jshn and list components. Moved runqueue and blobmsg from examples to tests. Converted just a few first test cases from json-script example into the new cram based unit test, more to come. Signed-off-by: Petr Štetiar <ynezz@true.cz> 2019-11-19 14:31:44 +01:00			`check that runqueue is producing expected results:`

			`$ [ -n "$TEST_BIN_DIR" ] && export PATH="$TEST_BIN_DIR:$PATH"`
			`$ valgrind --quiet --leak-check=full test-runqueue`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`All done!`
tests: add unit tests covered with Clang sanitizers Currently we run all tests via Valgrind. This patch adds 2nd batch of tests which are compiled with Clang AddressSanitizer[1], LeakSanitizer[2] and UndefinedBehaviorSanitizer[3] in order to catch more issues during QA on CI. AddressSanitizer is a fast memory error detector. The tool can detect the following types of bugs: * Out-of-bounds accesses to heap, stack and globals * Use-after-free, use-after-return, use-after-scope * Double-free, invalid free LeakSanitizer is a run-time memory leak detector. It can be combined with AddressSanitizer to get both memory error and leak detection, or used in a stand-alone mode. UndefinedBehaviorSanitizer (UBSan) is a fast undefined behavior detector. UBSan modifies the program at compile-time to catch various kinds of undefined behavior during program execution, for example: * Using misaligned or null pointer * Signed integer overflow * Conversion to, from, or between floating-point types which would overflow the destination 1. http://clang.llvm.org/docs/AddressSanitizer.html 2. http://http://clang.llvm.org/docs/LeakSanitizer.html 3. http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html Signed-off-by: Petr Štetiar <ynezz@true.cz> 2019-12-08 13:12:47 +01:00
			`$ test-runqueue-san`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`[1/1] start 'sleep 1'`
			`[1/1] cancel 'sleep 1'`
			`[0/1] finish 'sleep 1'`
			`All done!`