Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot runtime test infrastructure prototype
Date: Tue, 30 Jun 2015 10:38:49 +0200 (CEST)	[thread overview]
Message-ID: <1581556904.2327180.1435653528950.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20150630093903.4fd27ca5@free-electrons.com>



> 
> Thanks a lot for giving more details about this. Indeed having a
> working example would be nice. However, I'm not entirely convinced
> this
> higher-level tabular format is really much more readable/useful than
> a
> pure Python solution. This higher-level tabular format remains in any
> case more limited than a real programming language, and it's a
> special
> syntax you have to learn, while Python is known by a large number of
> people already.
> 

We are in the process of reimplementing your examples in RFW to provide
some food for thought, stay tuned...

> But maybe I would be more convinced by some other features of RFW.
> What
> are its reporting capabilities?

pretty good, RFW can report in an xunit-compatible xml which can be
easily parsed by whatever tool you prefer. I have been autogenerating
reports with it for quite some time

RFW also generates some HTML pages ready to be pushed on a server,
but that's less usefull for the buildroot use-case.

An exemple of generated HTML can be found here:

http://robotframework.org/robotframework/latest/images/log_passed.html

> Can it run tests in parallel?

no, RFW core has no parallel testing capabilities by itself. There 
are plugins to do that, though...

> Can we
> easily integrate the tests with Jenkins to have them run everyday?

RFW has its own jenkins plugin to harness test results. integration
is very easy

the plugin is available here :

https://wiki.jenkins-ci.org/display/JENKINS/Robot+Framework+Plugin


> 
> Thanks,
> 
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> 

  reply	other threads:[~2015-06-30  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 18:02 [Buildroot] Buildroot runtime test infrastructure prototype Thomas Petazzoni
2015-06-26 15:48 ` Andreas Naumann
2015-06-26 16:20   ` Jeremy Rosen
2015-06-28  9:50     ` Thomas Petazzoni
2015-06-30  7:06       ` Andreas Naumann
2015-06-30  7:39         ` Thomas Petazzoni
2015-06-30  8:38           ` Jeremy Rosen [this message]
2015-06-30  8:46             ` Thomas Petazzoni
2015-06-30 20:26             ` Andreas Naumann
2015-07-01  8:53               ` Jeremy Rosen
2015-06-30 16:06       ` Jeremy Rosen
2015-07-01  7:30         ` Andreas Naumann
2015-07-01  7:57           ` Jeremy Rosen
2015-07-01 10:28           ` Denis Thulin
2015-07-02 13:57             ` Andreas Naumann
2015-06-26 18:12 ` Thomas De Schampheleire
2015-06-26 18:26   ` Thomas De Schampheleire

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=1581556904.2327180.1435653528950.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --cc=buildroot@busybox.net \
    /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