zephyr/tests/kernel/test_obj_tracing/microkernel
Inaky Perez-Gonzalez fcec9e37c0 testcases: sanity check TCs get more language for real HW
Add more specifications or qualify some to the sanity check test cases
for them to be ran in real hardware:

 - kernel types (micro vs nano)
 - platforms / arches to exclude / include
 - one that is removed (for the PCI sample) as it cannot be ran
   without extra information

Change-Id: Id14dc15eb89358c3656d2814ea41bb6fec051278
Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
2016-06-14 23:49:56 +00:00
..
src debug: add task tracing to sanity test 2016-03-11 22:13:43 +00:00
Makefile tests: remove duplicate kernel configs and usage of ARCH 2016-05-23 16:46:08 +00:00
prj.conf tests: remove duplicate kernel configs and usage of ARCH 2016-05-23 16:46:08 +00:00
prj.mdef debug: sanity test for kernel object tracing 2016-03-11 22:07:15 +00:00
README.txt debug: sanity test for kernel object tracing 2016-03-11 22:07:15 +00:00
testcase.ini testcases: sanity check TCs get more language for real HW 2016-06-14 23:49:56 +00:00

Test Description
----------------

The object tracing test is a sanity test to verify that the
object tracing API remains healthy on both the nanokernel and
microkernel.

It uses the philsophers as a common application that implements
multiple taks that are synchronized with mutexes.

The application initializes their objects and starts the philosophers'
task interaction. A specific task, called object monitor, accesses
the object tracing API and reports the number of expected objects.

The sanity test script expects each test to finish its execution
and then it considers the test completed. For that reason the
philosophers' threads execute a finite number of iterations. After
that the application execution ends.