From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC: Testing U-Boot Part 1
Date: Fri, 26 Aug 2011 00:21:43 +0200 [thread overview]
Message-ID: <201108260021.43506.marek.vasut@gmail.com> (raw)
In-Reply-To: <201108251056.41026.vapier@gentoo.org>
On Thursday, August 25, 2011 04:56:39 PM Mike Frysinger wrote:
> On Thursday, August 25, 2011 09:56:02 Andreas Bie?mann wrote:
> > Am 25.08.2011 14:58, schrieb Simon Glass:
> > > Summary: I am quite keen on improving the test infrastructure in
> > > U-Boot. I would like to have a test suite that can run in a minute or
> > > two on a Linux PC and test all non-platform code.
> >
> > <snip>
> >
> > > To get around this I propose that we create a new ?native?
> > > architecture. We write code in ?arch/native? which can run under
> > > Linux. Since all the non-platform code will happily run under this new
> > > ?architecture?, we can then write tests which run quickly under x86
> > > Linux (or another Linux for that matter). This U-Boot 'architecture'
> > > should build natively on any 32/64-bit Linux machine since it just
> > > uses standard Linux system calls. Calls to Linux would be entirely
> > > within this arch/native subdirectory.
> >
> > why don't use some unit testing framework like cunit, or ceedling (which
> > can do HW mocks easily)?
>
> these testing frameworks wont make any difference to what Simon is
> proposing. he is focusing on getting u-boot to build & run on your desktop
> machine. after that is done, we can talk about the actual tests and
> harnesses (although anything that requires ruby should immediately be
> disqualified imo :P). -mike
Definitelly agree with the RUBY part.
next prev parent reply other threads:[~2011-08-25 22:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 12:58 [U-Boot] RFC: Testing U-Boot Part 1 Simon Glass
2011-08-25 13:56 ` Andreas Bießmann
2011-08-25 14:56 ` Mike Frysinger
2011-08-25 22:21 ` Marek Vasut [this message]
2011-08-25 14:45 ` Marek Vasut
2011-08-25 15:01 ` Mike Frysinger
2011-08-25 18:04 ` Anton Staaf
2011-08-25 23:35 ` Graeme Russ
2011-08-26 3:32 ` Simon Glass
2011-08-26 4:36 ` Graeme Russ
2011-08-26 20:59 ` Mike Frysinger
2011-08-27 0:29 ` Simon Glass
2011-08-26 20:55 ` Mike Frysinger
2011-08-27 0:25 ` Simon Glass
2011-08-27 2:23 ` Graeme Russ
2011-08-29 22:04 ` Simon Glass
2011-08-29 23:03 ` Graeme Russ
2011-08-25 20:21 ` Wolfgang Denk
2011-08-25 21:18 ` 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=201108260021.43506.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--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