[Automated-testing] Glossary words unfamiliar to enterprise testers

[Tim.Bird at sony.com]

> -----Original Message-----
> From: Neil Williams [mailto:neil.williams at linaro.org]
> Sent: Tuesday, October 30, 2018 1:19 AM
> 
> On Tue, 30 Oct 2018 at 08:16, Geert Uytterhoeven <geert at linux-m68k.org>
> wrote:
> >
> > On Tue, Oct 30, 2018 at 4:49 AM <Tim.Bird at sony.com> wrote:
> > > P.S. Anyone else on the list who would like to mark terms that were
> originally
> > > unfamiliar to them, can do so as well.  Just reply-all to this e-mail, and
> mark
> > > the unfamiliar or problematic items with a hash sign.
> > >
> > > Here is the originally-posted glossary:
> >
> > # * Provision (verb) - arrange the DUT and the lab environment
> > (including other external hardware) for a test
> >
> 
> LAVA has been building a glossary for a while:
> https://master.lavasoftware.org/static/docs/v2/glossary.html
> 
> We've also started with a naming convention:
> https://master.lavasoftware.org/static/docs/v2/naming-
> conventions.html#naming-conventions-and-lava-architecture
> 
> Rather than limiting to a single line, we include context and links
> into the rest of the documentation where there are examples and
> reference guides.

Those are good resources for understanding LAVA.  Fuego has a glossary
as well, for its terminology:  http://fuegotest.org/wiki/Glossary.

I'm going to create a testing glossary page on the elinux wiki based on the
initial survey results so far.   I'll try to put links to project-specific
glossaries on that page as well, as I think it will help with understanding
the different terms.

As we start comparing different terminologies, we may find that we
have different words for the same concept (or we may find that we
use substantially similar words for certain concepts).  In any
event I hope we can refine the shared glossary over time to improve
communication between projects.
 -- Tim