Hello,

 

Currently for the developing and running of the lava tests, we always run on the Lava master machine through lavacli. But we would like to skip the part of the running the tests from the lava master machine while developing, testing and triaging the tests written in the lava. We only want to run tests which are tested correctly to be run on through ci/cd on the lava master and for development, triaging we want to only use the lava-worker and board.  We only want to use the lava master only through CI/CD. 

Why not using the server for tests? You can have multiple users and use a specific user for CI/CD and another one for testing LAVA jobs.

 

Is there any way to run tests directly from the lava worker instead of going through lava master.  I tried "lava-test-shell" and "lava-dispatcher" but it didnt work for me. Can I use the lava api for developing and triaging the test scripts?

Yes but that's not easy and usually only used by LAVA developers.

You will have to call lava-run (part of the lava-dispatcher package) directly and call it with the right configuration files. The configuration files are saved as artifacts of each jobs and can be downloaded from the job page, Click on the red "Action" button then on Configuration.

 

Can you please recommend the best practice or setup for developing, testing and triaging the tests written in the lava? so that anyone can run, develop or modify tests quickly and make sure its successful and then only it can run through the lava master machine.

We usually use the production instances for this so the main option will be to use lava-run as described above.

Rgds

-- 

Rémi Duraffort

Principal Tech Lead

LAVA Tech Lead

Automation Software Team

Linaro

_______________________________________________
lava-users mailing list -- lava-users@lists.lavasoftware.org
To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s