From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC PATCH] Add u-boot command regression tests.
Date: Mon, 26 Nov 2007 00:29:20 +0100 [thread overview]
Message-ID: <20071125232920.C2FF9246B5@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 23 Nov 2007 20:03:38 EST." <20071124010338.GA27628@cideas.com>
Hello,
in message <20071124010338.GA27628@cideas.com> you wrote:
>
> ...and now, for something completely different.
>
> The concept here is to use PyUnit testing in conjunction with python
> serial I/O (theoretically, ethernet-based command I/O could be handled
> too).
>
> This is a concept probably sufficiently implemented for the "help"
> command and a good start for the "fdt" command.
>
> What does The List think?
> * Useful to have regression tests for the u-boot commands?
It is not only useful, but IMHO absolutely necessary to do regular
regression testing on U-Boot.
> * Implementation-wise, am I heading in the right direction?
I wish you had asked that question before spending efforts on this.
The point is, that there is already a pretty extensive and extandable
regression test suite for U-Boot (and Linux, and some more). We just
failed to announce it loudly enough (which clearly shows that DENX is
not marketing driven - and funny enough, I'm not a bit ashamed about
that). However, I'm sad about the avoidable duplication of efforts,
so I have to say I'm sorry.
Please have a look at the DUTS, our regression test suite. See the
git repo at http://www.denx.de/cgi-bin/gitweb.cgi?p=duts.git;a=summary
and some documentation at http://www.denx.de/wiki/DUTS/DUTSDocs
I'd really appreciate if this was picked up by others as well. [It
took us a long and winded road to get there - trying some existing
solutions like dejagnu etc. and finally ending with a do-it-yourself
solution.]
Note: there is a non-abvious benefit from the DUTS: once you got it
running on a board, it will generate a set of log files which just
need to be uploaded to our web server to generate a new version of
the DULG for this board. The idea is that if you have a new software
version you just need to run the DUTS to get (1) a confirmation that
everything is working as expected fromt he regression test suite and
(2) an updated version of the documentation with eexamples showing
exacly this software version on exactly that hardware.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Es gibt immer genug fuer die Beduerfnisse aller, aber niemals genug
fuer die Gier einzelner. -- Ghandi
next prev parent reply other threads:[~2007-11-25 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 1:03 [U-Boot-Users] [RFC PATCH] Add u-boot command regression tests Jerry Van Baren
2007-11-25 23:29 ` Wolfgang Denk [this message]
2007-11-26 13:49 ` Jerry Van Baren
2007-11-26 14:09 ` Wolfgang Denk
2007-11-27 22:46 ` Robert Schwebel
2007-11-28 2:32 ` gvb.uboot
2007-11-28 17:13 ` Robert Schwebel
2007-11-27 23:30 ` Kumar Gala
2007-11-28 0:58 ` gvb.uboot
2007-11-28 18:11 ` Mike Frysinger
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=20071125232920.C2FF9246B5@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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