User Tools

Site Tools


agl-testframework

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
agl-testframework [2016/07/14 05:09]
jsmoeller
agl-testframework [2016/07/14 05:40]
jsmoeller
Line 11: 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.
  
 +===== 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.
 +  * Remote Labs - to distribute the boards across sites and manage them, you need LAVA.
  
 ===== Workflow ===== ===== Workflow =====
agl-testframework.txt ยท Last modified: 2019/04/02 10:02 by pmarzin