From: "simon.kallweit@intefo.ch" <simon.kallweit@intefo.ch>
To: Christian Meusel <christian.meusel@inf.tu-dresden.de>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Cortex-M3 port
Date: Fri, 24 Oct 2008 12:25:00 -0000 [thread overview]
Message-ID: <4901B30C.4090406@intefo.ch> (raw)
In-Reply-To: <4901B0DC.4010208@inf.tu-dresden.de>
Christian Meusel wrote:
> Hello Simon,
>
>> * Is there any interest in getting some community driven automatic
>> testing infrastructure up and running? The current state is ok for
>> doing single tests from time to time, but not to have an automated
>> process. I'll further work with qmtest to automate our internal
>> testing, but I wonder if there is interest to do this development in
>> the community?
>
> I'm currently working on a port of eCos to a ColdFire MCF5282 and
> started running first tests. Running tests from the configtool or
> manually does not provide me the comfort im used to when doing unit
> testing.
>
> I have no experience with QMTest but having a framework which allows
> me to run a bunch of tests automatically on a target would be great.
> Especially when it allows to integrate tools for asserting hardware
> resets to the target.
If you are interested, check out the my SVN repo at
https://svn.inthemill.ch/ecos-cortex/trunk
There is a scripts/qmtest folder which contains the qmtest class I
wrote. This is just a proof-of-concept right now, nothing really
serious. What it does is basically using OpenOCD/Telnet to flash a test
binary, open a serial console for logging, doing a reset, and letting
the test run, collecting it's output. The output is then parsed (using
the semantics defined for ecos tests) and a test result is generated.
This is all very targeted towards my needs right now, but it could be
divided up into smaller components using qmtest. We could for example
abstract the actual running of the test from the parsing of the test's
output. This way we could run tests using the GDB support in redboot,
using JTAGs, using a simulator or whatever. The nice thing about qmtest
is that you get a good tool for organizing your tests,
starting/controlling batch runs, and examining the results. This can be
all done either using CLI or a simple embedded webserver.
Let me know what you think about it.
Simon
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-10-24 11:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 8:33 simon.kallweit
2008-10-24 8:44 ` Andrew Lunn
2008-10-24 10:16 ` simon.kallweit
2008-10-28 23:12 ` Chris Zimman
2008-10-29 0:28 ` [ECOS] " Grant Edwards
2008-10-29 1:37 ` [ECOS] Migrating away from CVS Chris Zimman
2008-10-29 6:07 ` [ECOS] " Grant Edwards
2008-10-29 8:48 ` simon.kallweit
2008-10-29 14:51 ` Grant Edwards
2008-11-04 22:52 ` Alexander Neundorf
2008-11-05 0:37 ` Frank Pagliughi
2008-11-05 0:40 ` Andy Jackson
2008-11-05 5:39 ` Grant Edwards
2008-11-05 7:11 ` Daniel Helgason
2008-11-05 8:46 ` simon.kallweit
2008-10-29 9:22 ` Ilija Kocho
2008-10-24 12:19 ` [ECOS] Cortex-M3 port Christian Meusel
2008-10-24 12:25 ` simon.kallweit [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 13:00 Alexander BORODULIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4901B30C.4090406@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=christian.meusel@inf.tu-dresden.de \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).