zephyr/tests/kernel/test_timer/nanokernel
Benjamin Walsh 87f1232770 unified/tests: tag working some tests kernel as 'unified_capable'
This allows running the sanitycheck with:

  --tag unified_capable -x KERNEL_TYPE=unified

to run the unified kernel with the tests it is currently known to be
able to run.

Change-Id: Ic145fc6adca162745887672372226fd67447b34a
Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-09-13 17:12:55 -04:00
..
src tests: kernel: fix incorrect printk() usage 2016-08-28 07:47:28 -04:00
Makefile test_timer: nanokernel: use empty config for all arches 2016-04-27 21:41:09 +00:00
prj.conf test_timer: nanokernel: use empty config for all arches 2016-04-27 21:41:09 +00:00
README.txt tests: move kernel tests to tests/ 2016-02-11 18:06:33 +00:00
testcase.ini unified/tests: tag working some tests kernel as 'unified_capable' 2016-09-13 17:12:55 -04:00

Title: Timer APIs

Description:

This test verifies that the nanokernel timer APIs operate as expected.

---------------------------------------------------------------------------

Building and Running Project:

This nanokernel project outputs to the console.  It can be built and executed
on QEMU as follows:

    make qemu

---------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

---------------------------------------------------------------------------

Sample Output:

tc_start() - Test Nanokernel Timer
Task testing basic timer functionality
  - test expected to take four seconds
Task testing timers expire in the correct order
  - test expected to take five or six seconds
Task testing the stopping of timers
  - test expected to take six seconds
Fiber testing basic timer functionality
  - test expected to take four seconds
Fiber testing timers expire in the correct order
  - test expected to take five or six seconds
Task testing the stopping of timers
  - test expected to take six seconds
Fiber to stop a timer that has a waiting fiber
Task to stop a timer that has a waiting fiber
PASS - main.
===================================================================
PROJECT EXECUTION SUCCESSFUL