LAVA server vs Yocto HW automation testing

From Yocto Project
Jump to: navigation, search
Lava server vs Yocto hardware automation testing
Tested steps Lava Yocto Comments
Controlling a board via serial connection Y Y
Booting a board via serial connection and bootloader using Yocto images artifacts Y Y
Able to schedule a test jobs to run at certain time N Y "Cron can be used in addition with lava CLI commands to trigger a test job"
Able to perform a full automated test cycle for a non serial connection board N Y "There is an issue with the test job which is exiting right after the master image ‘reboot’ command in order to boot into the test image as the master image ssh connection is lost and cannot run the next configu#FF6347 steps from the test job.Opened an enhancement for this at linaro but they told me that this feature will not be implemented for the dummy-ssh devices (https://bugs.linaro.org/show_bug.cgi?id=478)"
Able to view the test jobs results as tables Y N
Able to view the test jobs results as graphical reports Y N
Able to query old test jobs results Y N
Can use existing connection scripts for the tested boards N Y
Does not require additional packages for master image N Y Aditional packages needs for master image for ssh - sshfs connection
Can use existing test definitions N Y Runtime tests definitions needs to be manually added
Can use existing test jobs N Y Tests jobs needs to be manually created
Web based interface support Y N
Can accept test results from external sources N Y There is no way to submit results from the tested bsp to the Lava server
Authentication user support for the web based interface Y N
Able to use Yocto images artifacts Y Y
Can use the existing master image configurations N Y "We need to generate a pair of authentication keys between lava server and the master image – password less authentication from lava-server to the master image – root is requi#FF6347;Master image and test image must have the .ssh/authorized_keys configu#FF6347."
Personal tools