Hi, I am not sure how this fits in with what we have so before I can support any changes of this scale and direction I need to understand:
1. Are all existing tests to be converted to this new framework? 2. How does this effect the existing eco-system support such as the `rtems-test` command and the documentation around that command? 3. What does 'T' in THE_T_TEST_FRAMEWORK_H stand for? I prefer we prefix RTEMS_ where it makes sense. 4. I see in another email you post a Sphinx generated report. What are those tests and what is used to capture and create that report and will this in time include all existing tests? Chris On 14/3/19 9:24 pm, Sebastian Huber wrote: > Update #3199. > --- > cpukit/Makefile.am | 11 + > cpukit/headers.am | 1 + > cpukit/include/t.h | 2128 > +++++++++++++++++++++++++++++++++ > cpukit/libtest/t-test-checks-eno.c | 145 +++ > cpukit/libtest/t-test-checks-psx.c | 17 + _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
