Lines Matching +full:test +full:-

1               Thread-Metric RTOS Test Suite
4 1. Thread-Metric Test Suite
6 The Thread-Metric test suite consists of 8 distinct RTOS
8 of an RTOS. The test measures the total number of RTOS events
12 1.1. Basic Processing Test
14 This is the baseline test consisting of a single thread. This
15 should execute the same on every operating system. Test values
17 relative to the difference between the values of this test.
19 1.2. Cooperative Scheduling Test
21 This test consists of 5 threads created at the same priority that
22 voluntarily release control to each other in a round-robin fashion.
24 the next thread.  At the end of the test the counters will be verified
27 result of the cooperative scheduling test.
29 1.3. Preemptive Scheduling Test
31 This test consists of 5 threads that each have a unique priority.
32 In this test, all threads except the lowest priority thread are
41 highest priority thread - starting the whole process over once again.
43 1.4. Interrupt Processing Test
45 This test consists of a single thread. The thread will cause an
49 interrupt handler completes, processing returns to the test
54 1.5. Interrupt Preemption Processing Test
56 This test is similar to the previous interrupt test. The big
57 difference is the interrupt handler in this test resumes a
60 1.6. Message Processing Test
62 This test consists of a thread sending a 16 byte message to a
67 1.7. Synchronization Processing Test
69 This test consists of a thread getting a semaphore and then
75 This test consists of a thread allocating a 128-byte block and
81 A few minor modifications have been made to the Thread-Metric source
84 2.1. tm_main() -> main()
92 than that used by the original Thread-Metric code. These functions
98 the reporting function directly. This helps ensure that the test
103 Each test has been converted to its own project. This has necessitated
107 The source code to the Thread-Metric test suite is organized into
112 tm_basic_processing_test.c                    Basic test for determining board
114 tm_cooperative_scheduling_test.c              Cooperative scheduling test
115 tm_preemptive_scheduling_test.c               Preemptive scheduling test
116 tm_interrupt_processing_test.c                No-preemption interrupt processing
117                                                  test
119                                                  test
120 tm_message_processing_test.c                  Message exchange processing test
121 tm_synchronization_processing_test.c          Semaphore get/put processing test
122 tm_memory_allocation_test.c                   Basic memory allocation test
126 2.5. Test execution with Twister tool
128 When the test suite is executed by Twister it takes parameters from testcase.yaml
134     * use 300 sec. timeout on each benchmark test from this suite;
162     initialization, calling the test initialization function as
195     one 16-byte message. If successful, a TM_SUCCESS is returned.
225     128-byte block of memory. If successful, a TM_SUCCESS is returned.
229     This function allocates a 128-byte block of memory from the
236     This function releases the previously allocated 128-byte block
243 are achieved on each RTOS performing the test: