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/14 05:09] jsmoeller |
agl-testframework [2016/07/14 05:38] jsmoeller |
||
---|---|---|---|
Line 10: | Line 10: | ||
* AGL-JTA/Fuego has an extensive predefined set of tests and strong reporting capabilities | * AGL-JTA/Fuego has an extensive predefined set of tests and strong reporting capabilities | ||
* 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. | ||
+ | |||
+ | ===== Use-cases ===== | ||
+ | From the above you can deduct the following use-cases: | ||
+ | |||
+ | * In-house lab - for an isolated, in-house lab, AGL-JTA/Fuego is likely your choice. With a small set of boards on the same network, you only need AGL-JTA/Fuego - no LAVA server is needed. | ||
+ | * Board-Farm - to scale-out the testing and parallelize the execution, we need to manage multiple boards of the same type/family and multiple different boards/brands. In this case you need LAVA to mange the boards. | ||