Re: [ECOS] ecos test infrastructure

[Alex Schuilenburg <alexs@ecoscentric.com>]

Andrew Lunn wrote:
>>Running a single test program from within gdb works fine.
>>Would it be possible with the current infrastructure to run a
>>testsuite on the target system without using the graphical configtool
>>and report the results to a database instead? [*]
>>
>>Is there any more documentation about the testing infrastructure
>>(e.g.~about the use of dejagnu) than what I found in user-, ref-, and
>>component writers guide and the above described README.host?
[...]
>>[*] I guess the test farm at ecoscentric must do something similar...
> 
> 
> I've never seen eCosCentric's code, since it is there interlectual
> property, but i guess it does.

It does :-)  Currently at 5,658,576 tests executed and counting with
results easily searchable and selectable by our engineers.

OOI, while the docs refer to dejagnu, while at Cynus and later planet
Red Hat, it became clear to us that while dejagnu is fine for driving
gcc and gdb tests, unfortunately it does not cut the mustard when it
comes to driving eCos tests. Generally, we have found that the
configtool testing capability fulfils the requirements of most
developers whose use anoncvs so have not taken that further.

As for our test farm, eCosCentric have spent a significant amount of
effort and investment developing a fully-automated eCos testing
infrastructure to help us produce eCosPro. It puts eCos through its
paces in ways that the configtool cannot but requires a similar
investment by anyone wanting to run their own test suite. This generally
puts the usefulness of such a tool beyond the scope of anyone other than
those wanting to make a living supporting eCos, which explains in part
why you have not seen it available in anoncvs :-)

-- Alex


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss