[Automated-testing] Test Stack Survey
Tim.Bird at sony.com
Tim.Bird at sony.com
Wed Oct 3 13:58:50 PDT 2018
> -----Original Message-----
> From: Kevin Hilman
>
> <Tim.Bird at sony.com> writes:
>
> >> -----Original Message-----
> >> From: Jan Lübbe
> >>
> >> Hi Tim and Kevin,
> >>
> >> below are the survey answers for labgrid.
> >>
> >> Regarding the diagram, one aspect of labgrid that is not represented
> >> there is the interactive access to boards in the lab during development
> >> (build a system image locally, login&debug, run a testsuite from the
> >> commandline). But with the focus on automated testing, that's probably
> >> fine. :)
> >
> > OK - noted on the wiki page I created. I think it's worth considering,
> because
> > although it's not directly used in automated testing, it does affect the
> > architecture, IMHO. And I believe some other systems support this.
...
> >> * Dependency - indicates a pre-requisite that must be filled in order for a
> test
> >> to run (e.g. must have root access, must have 100 meg of memory, some
> >> program must be installed, etc.)
> >> '''These are called "features" in labgrid'''
> >>
> >> '''Missing is the concept of a collection of similar DUTs, as used when
> >> scheduling a test on one of many DUTs.'''
> >
> > Noted. Do you have a term for this that you use? I would suggest 'DUT
> pool', but
> > that's just off the top of my head. I think other systems have similar
> notions:
> > a collection of DUTs with similar features any of which could be used to
> > execute a particular test (or which could be used to pipeline multiple tests
> > against the same SUT to save time.)
> >
> > I think it would be good to have a common term for this.
>
> The LAVA terminolgy might be useful here (and already familiar to
> some). In LAVA this is called a "device type", referring to a specific
> class/group of similar/identical boards. A specific instance is called
> a "device" in LAVA.
I put some candidate terms in the glossary on the survey page, that
we can discuss either by email or at the summit. See
https://elinux.org/Test_Stack_Survey#Candidate_terms
-- Tim
More information about the automated-testing
mailing list