All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@gmail.com>
Cc: dan.rue@linaro.org, tomeu.vizoso@collabora.com, kernelci@groups.io
Subject: Re: [kernelci] Meeting Minutes for 2018-08-20
Date: Fri, 24 Aug 2018 09:43:14 -0700	[thread overview]
Message-ID: <7hzhxb4swt.fsf@baylibre.com> (raw)
In-Reply-To: <CAH1_8nBKSwYDetOTJR-a3Nzv-La9=SiqMbENoVVn9D0hhSTQ4A@mail.gmail.com> (Guillaume Tucker's message of "Thu, 23 Aug 2018 08:35:33 +0100")

Guillaume Tucker <guillaume.tucker@gmail.com> writes:

[...]

> I like Kevin's suggestion of having sets in sets, in fact that's
> something we were discussing yesterday with Ana.  Here's a
> pseudo-schema I think would work well:
>
> TestCase:
>   * name
>   * result
>   * meta-data
>
> TestGroup:
>   * name
>   * meta-data
>   * list of test cases
>   * list of test groups
>
> Think of it a bit like a file system, with groups being
> directories and cases files.  You can have groups within
> groups...  This can scale both ways, to have sets within suites,
> and also suites within a collection of suites or whatever we want
> to do with this.  Then we can have a way of calling them with
> some kind of path like suite/set/case, or suite.set.case, or just
> suite.case, or super-plan.suite.case or whatever it takes to
> store the test suite results.
>
> I believe the changes should be relatively simple, and should
> result in a simpler database schema than what we have now with
> suites & sets mixed up.

I like it!  Can support relatively flat (like we have today) or
arbitrary scaling.  

Kevin


  reply	other threads:[~2018-08-24 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 16:28 Meeting Minutes for 2018-08-20 Dan Rue
2018-08-20 18:45 ` [kernelci] " Kevin Hilman
2018-08-20 20:20   ` Guillaume Tucker
2018-08-20 21:07     ` Mark Brown
2018-08-20 23:52     ` Kevin Hilman
2018-08-22 10:11       ` Tomeu Vizoso
2018-08-22 17:20         ` Dan Rue
2018-08-23  3:50           ` Kevin Hilman
2018-08-23  7:35             ` Guillaume Tucker
2018-08-24 16:43               ` Kevin Hilman [this message]
2018-08-23  3:40         ` Kevin Hilman
2018-08-23  7:35           ` Milosz Wasilewski
2018-08-21 10:20     ` Milosz Wasilewski
2018-08-22 16:19       ` Guillaume Tucker

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=7hzhxb4swt.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=dan.rue@linaro.org \
    --cc=guillaume.tucker@gmail.com \
    --cc=kernelci@groups.io \
    --cc=tomeu.vizoso@collabora.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 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.