|
|
Tims LAVA Notes in split format
|
Here are some notes about the LAVA system:
|
Here are some notes about the LAVA system:
|
|
(need to add more of my notes from Linaro connect 2016 (Las Vegas) here)
|
(need to add more of my notes from Linaro connect 2016 (Las Vegas) here)
|
|
|
= target dictionary =
LAVA V2 has something called a "target dictionary", which hold values
for a board.
|
|
The LAVA developers have a model that allows for multiple layers of
values to be held, and inheritance and overrides to be used for the
variables used for actual testing.
|
The LAVA developers have a model that allows for multiple layers of
values to be held, and inheritance and overrides to be used for the
variables used for actual testing.
|
|
They appear to put different types of variables into different format
files, throughout the system, and use a database to query and manage
the variables.
|
They appear to put different types of variables into different format
files, throughout the system, and use a database to query and manage
the variables.
|
|
|
= test materials =
LAVA does not, itself, serve as a repository for test materials.
|
|
As a test framework, it "knows" how to perform actions on boards,
but it doesn't actually have the tests in its own repository.
The test to run is left as an exercise for the user.
|
As a test framework, it "knows" how to perform actions on boards,
but it doesn't actually have the tests in its own repository.
The test to run is left as an exercise for the user.
|
|
|
= security =
There is a security model which allows for tight control of test operations.
IMHO, this should be left as an exercise for Jenkins.
|
|
|