As described in remote-resources-and-places
, one of labgrid's main features is granting access to boards connected to other hosts transparent for the client. To get started with remote access, take a look at remote-getting-started
.
When sharing places between developers or with CI jobs, it soon becomes necessary to manage who can access which places. Developers often just need any place which has one of a group of identical devices, while CI jobs should wait until the necessary place is free instead of failing.
To support these use-cases, the coordinator has support for reserving places by using a tag filter and an optional priority. First, the places have to be tagged with the relevant key-value pairs:
$ labgrid-client -p board-1 set-tags board=imx6-foo
$ labgrid-client -p board-2 set-tags board=imx6-foo
$ labgrid-client -p board-3 set-tags board=imx8m-bar
$ labgrid-client -v places
Place 'board-1':
tags: bar=baz, board=imx6-foo, jlu=2, rcz=1
matches:
rl-test/Testport1/NetworkSerialPort
…
Place 'board-2':
tags: board=imx6-foo
matches:
rl-test/Testport2/NetworkSerialPort
…
Place 'board-3':
tags: board=imx8m-bar
matches:
rl-test/Testport3/NetworkSerialPort
…
Now, if you want to access any imx6-foo
board, you could find that all are already in use by someone else:
$ labgrid-client who
User Host Place Changed
rcz dude board-1 2019-08-06 12:14:38.446201
jenkins worker1 board-2 2019-08-06 12:52:44.762131
In this case, you can create a reservation. You can specify any custom tags as part of the filter, as well as name=<place-name>
to select only a specific place (even if it has no custom tags).
$ labgrid-client reserve board=imx6-foo
Reservation 'SP37P5OQRU':
owner: rettich/jlu
token: SP37P5OQRU
state: waiting
filters:
main: board=imx6-foo
created: 2019-08-06 12:56:49.779982
timeout: 2019-08-06 12:57:49.779983
As soon as any matching place becomes free, the reservation state will change from waiting
to allocated
. Then, you can use the reservation token prefixed by +
to refer to the allocated place for locking and usage. While a place is allocated for a reservation, only the owner of the reservation can lock that place.
$ labgrid-client wait SP37P5OQRU
owner: rettich/jlu
token: SP37P5OQRU
state: waiting
filters:
main: board=imx6-foo
created: 2019-08-06 12:56:49.779982
timeout: 2019-08-06 12:58:14.900621
…
owner: rettich/jlu
token: SP37P5OQRU
state: allocated
filters:
main: board=imx6-foo
allocations:
main: board-2
created: 2019-08-06 12:56:49.779982
timeout: 2019-08-06 12:58:46.145851
$ labgrid-client -p +SP37P5OQRU lock
acquired place board-2
$ labgrid-client reservations
Reservation 'SP37P5OQRU':
owner: rettich/jlu
token: SP37P5OQRU
state: acquired
filters:
main: board=imx6-foo
allocations:
main: board-2
created: 2019-08-06 12:56:49.779982
timeout: 2019-08-06 12:59:11.840780
$ labgrid-client -p +SP37P5OQRU console
When using reservation in a CI job or to save some typing, the labgrid-client reserve
command supports a --shell
command to print code for evaluating in the shell. This sets the LG_TOKEN
environment variable, which is then automatically used by wait
and expanded via -p +
.
$ eval `labgrid-client reserve --shell board=imx6-foo`
$ echo $LG_TOKEN
ZDMZJZNLBF
$ labgrid-client wait
owner: rettich/jlu
token: ZDMZJZNLBF
state: waiting
filters:
main: board=imx6-foo
created: 2019-08-06 13:05:30.987072
timeout: 2019-08-06 13:06:44.629736
…
owner: rettich/jlu
token: ZDMZJZNLBF
state: allocated
filters:
main: board=imx6-foo
allocations:
main: board-1
created: 2019-08-06 13:05:30.987072
timeout: 2019-08-06 13:06:56.196684
$ labgrid-client -p + lock
acquired place board-1
$ labgrid-client -p + show
Place 'board-1':
tags: bar=baz, board=imx6-foo, jlu=2, rcz=1
matches:
rettich/Testport1/NetworkSerialPort
acquired: rettich/jlu
acquired resources:
created: 2019-07-29 16:11:52.006269
changed: 2019-08-06 13:06:09.667682
reservation: ZDMZJZNLBF
Finally, to avoid calling the wait
command explicitly, you can add --wait
to the reserve
command, so it waits until the reservation is allocated before returning.
A reservation will time out after a short time, if it is neither refreshed nor used by locked places.
labgrid can be used directly as a Python library, without the infrastructure provided by the pytest plugin.
The labgrid library provides two ways to configure targets with resources and drivers: either create the Target
directly or use Environment
to load a configuration file.
At the lower level, a Target
can be created directly:
>>> from labgrid import Target
>>> t = Target('example')
Next, the required Resources <Resource>
can be created:
>>> from labgrid.resource import RawSerialPort
>>> rsp = RawSerialPort(t, name=None, port='/dev/ttyUSB0')
Note
Since we support multiple drivers of the same type, resources and drivers have a required name attribute. If you don't require support for this functionality set the name to None.
Then, a Driver
needs to be created on the `Target`:
>>> from labgrid.driver import SerialDriver
>>> sd = SerialDriver(t, name=None)
As the SerialDriver declares a binding to a SerialPort, the target binds it to the resource created above:
>>> sd.port
RawSerialPort(target=Target(name='example', env=None), name=None, state=<BindingState.bound: 1>, avail=True, port='/dev/ttyUSB0', speed=115200)
>>> sd.port is rsp
True
Before the driver can be used, it needs to be activated:
>>> t.activate(sd)
>>> sd.write(b'test')
Active drivers can be accessed by class (any Driver or Protocol) using some syntactic sugar:
>>> target = Target('main')
>>> console = FakeConsoleDriver(target, 'console')
>>> target.activate(console)
>>> target[FakeConsoleDriver]
FakeConsoleDriver(target=Target(name='main', …), name='console', …)
>>> target[FakeConsoleDriver, 'console']
FakeConsoleDriver(target=Target(name='main', …), name='console', …)
In practice, is is often useful to separate the Target configuration from the code which needs to control the board (such as a test case or installation script). For this use-case, labgrid can construct targets from a configuration file in YAML format:
targets:
example:
resources:
RawSerialPort:
port: '/dev/ttyUSB0'
drivers:
SerialDriver: {}
To parse this configuration file, use the Environment
class:
>>> from labgrid import Environment
>>> env = Environment('example-env.yaml')
Using Environment.get_target
, the configured Targets can be retrieved by name. Without an argument, get_target would default to 'main':
>>> t = env.get_target('example')
To access the target's console, the correct driver object can be found by using Target.get_driver
:
>>> from labgrid.protocol import ConsoleProtocol
>>> cp = t.get_driver(ConsoleProtocol)
>>> cp
SerialDriver(target=Target(name='example', env=Environment(config_file='example.yaml')), name=None, state=<BindingState.active: 2>, txdelay=0.0)
>>> cp.write(b'test')
When using the get_driver
method, the driver is automatically activated. The driver activation will also wait for unavailable resources when needed.
For more information on the environment configuration files and the usage of multiple drivers, see configuration:Environment Configuration
.
labgrid includes a pytest plugin to simplify writing tests which involve embedded boards. The plugin is configured by providing an environment config file (via the --lg-env pytest option, or the LG_ENV environment variable) and automatically creates the targets described in the environment.
Two pytest fixtures are provided:
- env (session scope)
Used to access the
Environment
object created from the configuration file. This is mostly used for defining custom fixtures at the test suite level.- target (session scope)
Used to access the 'main'
Target
defined in the configuration file.
The pytest plugin also supports the verbosity argument of pytest:
-vv
: activates the step reporting feature, showing function parameters and/or results-vvv
: activates debug logging
This allows debugging during the writing of tests and inspection during test runs.
Other labgrid-related pytest plugin options are:
--lg-env=LG_ENV
(was--env-config=ENV_CONFIG
)Specify a labgrid environment config file. This is equivalent to labgrid-client's
-c
/--config
.--lg-coordinator=CROSSBAR_URL
Specify labgrid coordinator websocket URL. Defaults to
ws://127.0.0.1:20408/ws
. This is equivalent to labgrid-client's-x
/--crossbar
.--lg-log=[path to logfiles]
Path to store console log file. If option is specified without path the current working directory is used.
--lg-colored-steps
Enables the ColoredStepReporter. Different events have different colors. The more colorful, the more important. In order to make less important output "blend into the background" different color schemes are available. See
LG_COLOR_SCHEME <usage-lgcolorscheme>
.
pytest --help
shows these options in a separate labgrid section.
Behaves like LG_ENV
for labgrid-client <man/client>
.
Influences the color scheme used for the Colored Step Reporter. dark
(default) is meant for dark terminal background. light
is optimized for light terminal background. Takes effect only when used with --lg-colored-steps
.
Specifies a SSH proxy host to be used for port forwards to access the coordinator and network resources.
As a minimal example, we have a target connected via a USB serial converter ('/dev/ttyUSB0') and booted to the Linux shell. The following environment config file (shell-example.yaml
) describes how to access this board:
targets:
main:
resources:
RawSerialPort:
port: '/dev/ttyUSB0'
drivers:
SerialDriver: {}
ShellDriver:
prompt: 'root@\w+:[^ ]+ '
login_prompt: ' login: '
username: 'root'
We then add the following test in a file called test_example.py
:
from labgrid.protocol import CommandProtocol
def test_echo(target):
command = target.get_driver(CommandProtocol)
result = command.run_check('echo OK')
assert 'OK' in result
To run this test, we simply execute pytest in the same directory with the environment config:
$ pytest --lg-env shell-example.yaml --verbose
============================= test session starts ==============================
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
…
collected 1 items
test_example.py::test_echo PASSED
=========================== 1 passed in 0.51 seconds ===========================
pytest has automatically found the test case and executed it on the target.
When writing many test cases which use the same driver, we can get rid of some common code by wrapping the CommandProtocol in a fixture. As pytest always executes the conftest.py
file in the test suite directory, we can define additional fixtures there:
import pytest
from labgrid.protocol import CommandProtocol
@pytest.fixture(scope='session')
def command(target):
return target.get_driver(CommandProtocol)
With this fixture, we can simplify the test_example.py
file to:
def test_echo(command):
result = command.run_check('echo OK')
assert 'OK' in result
When using a Strategy
to transition the target between states, it is useful to define a function scope fixture per state in conftest.py
:
import pytest
from labgrid.protocol import CommandProtocol
from labgrid.strategy import BareboxStrategy
@pytest.fixture(scope='session')
def strategy(target):
try:
return target.get_driver(BareboxStrategy)
except NoDriverFoundError:
pytest.skip("strategy not found")
@pytest.fixture(scope='function')
def switch_off(target, strategy, capsys):
with capsys.disabled():
strategy.transition('off')
@pytest.fixture(scope='function')
def bootloader_command(target, strategy, capsys):
with capsys.disabled():
strategy.transition('barebox')
return target.get_active_driver(CommandProtocol)
@pytest.fixture(scope='function')
def shell_command(target, strategy, capsys):
with capsys.disabled():
strategy.transition('shell')
return target.get_active_driver(CommandProtocol)
Note
The capsys.disabled()
context manager is only needed when using the ManualPowerDriver
, as it will not be able to access the console otherwise. See the corresponding pytest documentation for details.
With the fixtures defined above, switching between bootloader and Linux shells is easy:
def test_barebox_initial(bootloader_command):
stdout = bootloader_command.run_check('version')
assert 'barebox' in '\n'.join(stdout)
def test_shell(shell_command):
stdout = shell_command.run_check('cat /proc/version')
assert 'Linux' in stdout[0]
def test_barebox_after_reboot(bootloader_command):
bootloader_command.run_check('true')
Note
The bootloader_command and shell_command fixtures use Target.get_active_driver
to get the currently active CommandProtocol driver (either BareboxDriver
or ShellDriver
). Activation and deactivation of drivers is handled by the BareboxStrategy
in this example.
The Strategy needs additional drivers to control the target. Adapt the following environment config file (strategy-example.yaml
) to your setup:
targets:
main:
resources:
RawSerialPort:
port: '/dev/ttyUSB0'
drivers:
ManualPowerDriver:
name: 'example-board'
SerialDriver: {}
BareboxDriver:
prompt: 'barebox@[^:]+:[^ ]+ '
ShellDriver:
prompt: 'root@\w+:[^ ]+ '
login_prompt: ' login: '
username: 'root'
BareboxStrategy: {}
For this example, you should get a report similar to this:
$ pytest --lg-env strategy-example.yaml -v
============================= test session starts ==============================
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
…
collected 3 items
test_strategy.py::test_barebox_initial
main: CYCLE the target example-board and press enter
PASSED
test_strategy.py::test_shell PASSED
test_strategy.py::test_barebox_after_reboot
main: CYCLE the target example-board and press enter
PASSED
========================== 3 passed in 29.77 seconds ===========================
labgrid includes support for feature flags on a global and target scope. Adding a @pytest.mark.lg_feature
decorator to a test ensures it is only executed if the desired feature is available:
import pytest
@pytest.mark.lg_feature("camera")
def test_camera(target):
[...]
Here's an example environment configuration:
targets:
main:
features:
- camera
resources: {}
drivers: {}
This would run the above test, however the following configuration would skip the test because of the missing feature:
targets:
main:
features:
- console
resources: {}
drivers: {}
pytest will record the missing feature as the skip reason.
For tests with multiple required features, pass them as a list to pytest:
import pytest
@pytest.mark.lg_feature(["camera", "console"])
def test_camera(target):
[...]
Features do not have to be set per target, they can also be set via the global features key:
features:
- camera
targets:
main:
features:
- console
resources: {}
drivers: {}
This YAML configuration would combine both the global and the target features.
With the pytest-html plugin, the test results can be converted directly to a single-page HTML report:
$ pip install pytest-html
$ pytest --lg-env shell-example.yaml --html=report.html
JUnit XML reports can be generated directly by pytest and are especially useful for use in CI systems such as Jenkins with the JUnit Plugin.
They can also be converted to other formats, such as HTML with junit2html tool:
$ pip install junit2html
$ pytest --lg-env shell-example.yaml --junit-xml=report.xml
$ junit2html report.xml
labgrid adds additional xml properties to a test run, these are:
- ENV_CONFIG: Name of the configuration file
- TARGETS: List of target names
- TARGET{NAME}_REMOTE: optional, if the target uses a RemotePlace resource, its name is recorded here
- PATH{NAME}: optional, labgrid records the name and path
- PATH{NAME}_GIT_COMMIT: optional, labgrid tries to record git sha1 values for every path
- IMAGE{NAME}: optional, labgrid records the name and path to the image
- IMAGE{NAME}_GIT_COMMIT: optional, labgrid tries to record git sha1 values for every image
labgrid contains some command line tools which are used for remote access to resources. See man/client
, man/device-config
and man/exporter
for more information.