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:38] jsmoeller |
agl-testframework [2016/07/14 05:40] jsmoeller |
||
---|---|---|---|
Line 16: | Line 16: | ||
* 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. | * 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. | * 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. | ||
+ | * Remote Labs - to distribute the boards across sites and manage them, you need LAVA. | ||
===== Workflow ===== | ===== Workflow ===== |