User Tools
agl-testframework
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
agl-testframework [2016/07/13 20:47] jsmoeller |
agl-testframework [2016/07/14 05:09] jsmoeller |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Introduction ===== | ||
| + | |||
| AGL uses a combination of tools for its CI tests. | AGL uses a combination of tools for its CI tests. | ||
| * AGL-JTA (a version of [[http://elinux.org/Fuego|Fuego]] is the frontend - more information can be found here: [[agl-jta|AGL-JTA]] | * AGL-JTA (a version of [[http://elinux.org/Fuego|Fuego]] is the frontend - more information can be found here: [[agl-jta|AGL-JTA]] | ||
| Line 9: | Line 11: | ||
| * LAVA is capable and excels at managing single boards and board-farms (power-up, deployment of filesystem and so on) and exposes a remote API. | * LAVA is capable and excels at managing single boards and board-farms (power-up, deployment of filesystem and so on) and exposes a remote API. | ||
| + | |||
| + | ===== Workflow ===== | ||
| + | |||
| + | The setup supports multiple operation methods: | ||
| + | * Code-change trigger: | ||
| + | * Gerrit triggers JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
| + | * Scripted trigger: | ||
| + | * Script triggers JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
| + | * Manual trigger: | ||
| + | * Manual trigger in JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
| + | * Direct test: | ||
| + | * Board allocation, bring-up and test execution through Lava. | ||
| + | |||
| + | ===== Setup ===== | ||
| A (WIP) documents describes the setup: [[agl-testframework/setup|SETUP]]. | A (WIP) documents describes the setup: [[agl-testframework/setup|SETUP]]. | ||
| - | + | ||
agl-testframework.txt · Last modified: 2020/05/20 01:59 by LiXiaoming
Page Tools
