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
Next revision Both sides next revision
agl-testframework [2016/07/14 05:38]
jsmoeller
agl-testframework [2019/04/02 10:02]
pmarzin
Line 3: Line 3:
 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]]
-  * [[https://​validation.linaro.org/​static/​docs/​index.html|Lava]] as tool to manage the boards remotely. ​+  * [[https://​validation.linaro.org/​static/​docs/v2/​index.html|Lava]] as tool to manage the boards remotely. ​
  
  
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 =====
agl-testframework.txt ยท Last modified: 2020/05/20 01:59 by LiXiaoming