All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Bur <cyrilbur@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: Testing
Date: Wed, 2 Dec 2015 10:50:59 +1100	[thread overview]
Message-ID: <20151202105059.1ebcc4dc@camb691> (raw)

Hi all,

I'd like to open some discussion about testing. I honestly haven't given that
much thought to big picture testing but I can describe what I'm doing to
btbridged to at least have something. I'm sure everyone has ideas as to which
direction the testing should be going and what we should be doing and this is
the conversation I would like to start.

At the moment it is almost impossible to test btbridged, short of actually
booting a real openbmc and making the host to something and through observation
try to see that all went well there really isn't a way of knowing if changes
work.

Joel kindly added a .travis.yml (travis-ci.org can automate) file to the
project to at least have compile checks, which is a great start. I'm currently
expanding on it so include a 'fake' bt-host and a trivial ipmi client. I don't
expect these tests to get too fancy but I do hope they'll be able to catch
broken commits. Future direction might be to have everything done in qemu so
that the 'fake' environment is closer to the real thing, doing so in qemu would
also allow us to test the bt-host driver in linux.

Cyril

             reply	other threads:[~2015-12-01 23:51 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 23:50 Cyril Bur [this message]
2015-12-03  4:58 ` Testing Stewart Smith
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21 17:44 Testing Turritopsis Dohrnii Teo En Ming
2019-05-27 13:42 Testing Turritopsis Dohrnii Teo En Ming
2018-12-14 19:23 Testing Tyler Baker
2017-05-02  6:37 Testing Oleg
2017-05-07 16:38 ` Testing Martin Blumenstingl
2017-05-07 17:36   ` Testing Oleg
2017-05-07 18:05     ` Testing Martin Blumenstingl
2017-05-07 18:55       ` Testing Oleg
     [not found]       ` <e7eb7d12-8fa8-5507-5d7b-53ef9ce3e300@yandex.ru>
2017-05-07 18:59         ` Testing Martin Blumenstingl
2017-05-07 19:09           ` Testing Oleg
2017-05-07 20:22             ` Testing Martin Blumenstingl
2017-05-07 20:44               ` Testing Oleg
2017-05-07 20:46                 ` Testing Martin Blumenstingl
2017-05-07 20:53                   ` Testing Oleg
2017-05-07 20:57                   ` Testing Oleg
2017-05-07 21:08                     ` Testing Martin Blumenstingl
2017-05-07 21:23                       ` Testing Oleg
2017-05-07 21:30                         ` Testing Martin Blumenstingl
2017-05-08  9:42                           ` Testing Oleg
2017-05-12  7:03   ` Testing Oleg
2017-05-25 18:35   ` Testing Tobias Baumann
2017-05-27 14:15     ` Testing Martin Blumenstingl
2017-05-27 14:57       ` Testing raptorsds
2017-05-27 16:08         ` Testing Martin Blumenstingl
2017-05-27 18:06           ` Testing raptorsds
2017-05-27 18:18             ` Testing Martin Blumenstingl
2015-03-15  8:57 Testing Teo En Ming (Zhang Enming)
2013-09-18 16:48 Testing Juan Casse
2013-09-18 16:45 Testing Juan Casse
2013-08-28 21:41 Testing David.Darrington
2012-12-27 18:38 testing Qin, Xiaohong
2012-04-18 14:11 testing simple w8
2011-03-26  3:16 Testing Martin Owens
2011-03-27  3:37 ` Testing Didier Spaier
     [not found]   ` <4D8EB10D.9060305-GqzDj6/B2j8@public.gmane.org>
2011-03-27 14:54     ` Testing Martin Owens
2011-03-27 15:49       ` Testing Didier Spaier
2011-04-01  6:54 ` Testing Christopher James Halse Rogers
2009-09-26 21:11 Testing Hal Rosenstock
2008-12-18 16:02 testing Bill O'Donnell
2007-09-28 14:11 Testing Richard Geddes
2003-03-16 11:54 testing Silvester Verdonskchot
2003-03-06 14:14 testing berthiaume_wayne
2003-03-06  9:16 testing Anders Widman
2003-03-06  9:14 testing Anders Widman
2003-02-13 21:43 testing Alan Powell
2003-02-13 21:28 testing Alan Powell
2002-11-19 11:58 testing Wasim Bashir
2002-01-15 17:30 Testing Daryl Woods
2002-01-15 17:30 ` Testing Daryl Woods
2001-11-30  9:58 Testing Jacky Costen
2001-11-24  4:07 testing Patrick McFarland
1999-06-06 17:47 testing Benjamin LaHaise
1999-03-12  1:36 testing David Miller
1999-03-12  1:42 ` testing David Miller
1998-03-19  0:23 testing Jamie Heller-Evans

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=20151202105059.1ebcc4dc@camb691 \
    --to=cyrilbur@gmail.com \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.