liblitmus.git/tests, branch 2010.2 [ARCHIVE] The userspace library for LITMUS^RT 2010. Now on GitHub. Add job control test case. 2010-02-26T15:42:43+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-02-26T15:42:43+00:00 2ace28d0725a47529a18ebac4c7c75bcf61446b9 Passes. 
Passes.
Add test for set_rt_task_param parameter validation. 2010-02-26T14:23:03+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-02-26T14:23:03+00:00 e3098fcce693f90fee6464233c075fbaddc04b07 All passed. 
All passed.
Add tests for invalid object types and od_open(). 2010-02-26T00:41:14+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-02-26T00:41:14+00:00 173c328f23f5c8b3519068f731a6db35488bbd25 






add test case for set_rt_task_param
2010-02-26T00:35:36+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-26T00:13:38+00:00

edd84612139b951dc511bfcc15619df0b64e79ab

Specifically, make sure invalid pointers are rejected.





Specifically, make sure invalid pointers are rejected.







Introduce test framework for LITMUS^RT.
2010-02-21T02:48:29+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-21T02:48:29+00:00

f3d21c128e5b40acd1f15e3ddcd7fd54ca3a9bed

This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.





This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.