Re: [PATCH 2/3] Add the T Test Framework

2019-03-21 Thread Sebastian Huber
On 20/03/2019 23:18, Chris Johns wrote: 3. What does 'T' in THE_T_TEST_FRAMEWORK_H stand for? I prefer we prefix RTEMS_ where it makes sense. The 'T' is just a random name which associates with testing. I searched a bit for and a T_ prefix and didn't found an existing project. So, there should

Re: [PATCH 2/3] Add the T Test Framework

2019-03-20 Thread Chris Johns
r) > { >     rtems_status_code sc; >     rtems_id id; >     rtems_id task; >     rtems_event_set events; > >     T_plan(8); >     T_step_true(0, T_is_runner(), "test body is not runner"); > >     sc = rtems_timer_create(rtems_build_name('T', 'E', 'S&#x

Re: [PATCH 2/3] Add the T Test Framework

2019-03-20 Thread Sebastian Huber
;id);     rtems_step_rsc_success(1, sc);     task = rtems_task_self();     sc = rtems_timer_fire_after(id, 1, wakeup, &task);     rtems_step_rsc_success(2, sc);     events = 0;     sc = rtems_event_receive(RTEMS_EVENT_0, RTEMS_WAIT | RTEMS_EVENT_ALL,         RTEMS_NO_TIMEOUT, &events);     rtem

Re: [PATCH 2/3] Add the T Test Framework

2019-03-19 Thread Chris Johns
screen capture update for the existing tests. >> 3. What does 'T' in THE_T_TEST_FRAMEWORK_H stand for? I prefer we prefix >> RTEMS_ >> where it makes sense. > > The 'T' is just a random name which associates with testing. I searched a bit > for and a T

Re: [PATCH 2/3] Add the T Test Framework

2019-03-19 Thread Sebastian Huber
T' in THE_T_TEST_FRAMEWORK_H stand for? I prefer we prefix RTEMS_ where it makes sense. The 'T' is just a random name which associates with testing. I searched a bit for and a T_ prefix and didn't found an existing project. So, there should be no name conflicts. It is short, so this is goo

Re: [PATCH 2/3] Add the T Test Framework

2019-03-18 Thread Chris Johns
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

Re: The T Test Framework

2019-01-03 Thread Sebastian Huber
On 06/12/2018 15:50, Sebastian Huber wrote: Hello, I updated the documentation draft: https://devel.rtems.org/raw-attachment/ticket/3199/contributor.pdf It includes now also a section for time services and code runtime measurements. It would be nice to get some feedback if the general API is

Re: The T Test Framework

2018-12-06 Thread Sebastian Huber
Hello, I updated the documentation draft: https://devel.rtems.org/raw-attachment/ticket/3199/contributor.pdf It includes now also a section for time services and code runtime measurements. It would be nice to get some feedback if the general API is all right, e.g. header file and T_* namespa

Re: The T Test Framework

2018-11-28 Thread Sebastian Huber
Hello, I changed the test runner API a bit. Now it is also possible to test the system initialization for example. The test output of the attached example test (derived from sptests/spsysinit01): A:sysinit S:Platform:RTEMS S:Compiler:7.3.0 20180125 (RTEMS 5, RSB 30da0c720b78eba16a3f5272206c0

The T Test Framework

2018-11-23 Thread Sebastian Huber
Hello, I had a bit of time to work on a new test framework for RTEMS: https://devel.rtems.org/ticket/3199 You can find a draft of the documentation here: https://devel.rtems.org/attachment/ticket/3199/contributor.pdf You can find a prototype implementation here: https://devel.rtems.org/attac