From: Janet Lomas <JLomas@yottayotta.com>
To: ecos discuss <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Automated Testing
Date: Thu, 26 Oct 2000 11:02:00 -0000 [thread overview]
Message-ID: <39F8713D.E828E062@YottaYotta.com> (raw)
Hi,
I'm testing our eCos builds on various platforms to ensure the sanity of
the build. Does anyone have any advice about automating the tests that
come with ecos?
We're a linux shop and I'm currently using my own perl scripts to
download to an evaluation board, start execution and monitor output via
a serial port. When a case exits the results are logged and the next
srec is sent to the board & run, etc.
We added a definition for CYGHWR_TEST_PROGRAM_EXIT and made a change to
the macro CYG_TEST_CHECK to call CYG_TEST_EXIT rather than
cyg_test_exit() which doesn't exit in our world (because
CYGBLD_ATTRIB_NORET doesn't get defined). So far it's working OK.
Any advice, comments, pointers are welcome.
Cheers,
Janet
--
Janet Lomas Phone: (780) 439-9000x266
Testing Team Lead Fax: (780) 439-8845
JLomas@YottaYotta.com www.yottayotta.com
YottaYotta Inc. - The Yottabyte NetStorage (tm) company
reply other threads:[~2000-10-26 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39F8713D.E828E062@YottaYotta.com \
--to=jlomas@yottayotta.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).