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
On 20/3/19 7:50 pm, Sebastian Huber wrote:
> On 20/03/2019 01:44, Chris Johns wrote:
>> On 19/3/19 7:10 pm, Sebastian Huber wrote:
>>> Hello Chris,
>>>
>>> On 19/03/2019 06:17, Chris Johns wrote:
Hi,
I am not sure how this fits in with what we have so before I can support
any
>
On 20/03/2019 01:44, Chris Johns wrote:
On 19/3/19 7:10 pm, Sebastian Huber wrote:
Hello Chris,
On 19/03/2019 06:17, Chris Johns wrote:
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 existi
On 19/3/19 7:10 pm, Sebastian Huber wrote:
> Hello Chris,
>
> On 19/03/2019 06:17, Chris Johns wrote:
>> 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 convert
Hello Chris,
On 19/03/2019 06:17, Chris Johns wrote:
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?
the main purpose for the new framew
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
