Hello, I am trying to understand how the result levels are constructed for example when I run "lavacli results <job-id>" I get an output looking like so : Results: * lava.git-repo-action [pass] * lava.test-overlay [pass] * lava.test-install-overlay [pass] * lava.test-runscript-overlay [pass] * lava.my_test_case_1 [pass] * lava.my_test_case_2[pass]
what I want to do is to have a test categories, for example * lava.category1.my_test_case_1[pass] * lava.category3.my_test_case_3[pass]
and so on. I tried adding tags and namespaces but the results are not impacted, Can someone please guide me through this or mention part of the documentation that might be helpful ?
Thanks in advance.
Hello,
by default, every lava actions (deploying, booting, starting the tests) are grouped into a test suite called "lava". When you add tests, the results for each individual tests are grouped into a specific test suite named after the information in the test action.
Le jeu. 15 juin 2023 à 15:16, gemad@outlook.com a écrit :
Hello, I am trying to understand how the result levels are constructed for example when I run "lavacli results <job-id>" I get an output looking like so : Results:
- lava.git-repo-action [pass]
- lava.test-overlay [pass]
- lava.test-install-overlay [pass]
- lava.test-runscript-overlay [pass]
- lava.my_test_case_1 [pass]
- lava.my_test_case_2[pass]
what I want to do is to have a test categories, for example
- lava.category1.my_test_case_1[pass]
- lava.category3.my_test_case_3[pass]
and so on. I tried adding tags and namespaces but the results are not impacted, Can someone please guide me through this or mention part of the documentation that might be helpful ?
Thanks in advance. _______________________________________________ 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
Thanks for your reply, I am not sure I got what you meant by "individual tests are grouped into a specific test suite named after the information in the test action." My question was, which attribute/information in the test definition determine the testsuite ?
Thanks
On Fri, Jun 16, 2023 at 9:40 AM gemad@outlook.com wrote:
Thanks for your reply, I am not sure I got what you meant by "individual tests are grouped into a specific test suite named after the information in the test action." My question was, which attribute/information in the test definition determine the testsuite ?
It's "name"
- test: definitions: - from: git name: network-basic path: automated/linux/network-basic/network-basic.yaml repository: http://github.com/linaro/test-definitions.git
Best Regards, Milosz
Thanks _______________________________________________ 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
Thanks for the reply, I will try to make my point more clear, So let assume I have many test cases related to the network-basic, should I repeat the this block with the same name and different paths ?
like I want the result to be :
* lava.network-basic.testcase1 [pass] * lava.network-basic.testcase2 [pass] * lava.network-basic.testcase3 [fail]
so In the job : - test: definitions: - from: git name: network-basic path: automated/linux/network-basic/testcase1.yaml repository: http://github.com/linaro/test-definitions.git - test: definitions: - from: git name: network-basic path: automated/linux/network-basic/testcase2.yaml repository: http://github.com/linaro/test-definitions.git - test: definitions: - from: git name: network-basic path: automated/linux/network-basic/testcase3.yaml repository: http://github.com/linaro/test-definitions.git
Thanks
On Fri, Jun 16, 2023 at 11:03 AM gemad@outlook.com wrote:
Thanks for the reply, I will try to make my point more clear, So let assume I have many test cases related to the network-basic, should I repeat the this block with the same name and different paths ?
LAVA won't let you do that. It will throw an error like this: Job error: Invalid job data: ['Test definition names need to be unique.']
like I want the result to be :
- lava.network-basic.testcase1 [pass]
- lava.network-basic.testcase2 [pass]
- lava.network-basic.testcase3 [fail]
so In the job :
- test: definitions:
- from: git name: network-basic path: automated/linux/network-basic/testcase1.yaml repository: http://github.com/linaro/test-definitions.git
- test: definitions:
- from: git name: network-basic path: automated/linux/network-basic/testcase2.yaml repository: http://github.com/linaro/test-definitions.git
- test: definitions:
- from: git name: network-basic path: automated/linux/network-basic/testcase3.yaml repository: http://github.com/linaro/test-definitions.git
You can have multiple test results produced by a single test-definition. I've no idea how this will work with lavacli. This is a very old tool based on XML-RPC which I believe isn't maintained any more. Remi will know better.
Best Regards, Milosz
Thanks _______________________________________________ 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
lava-users@lists.lavasoftware.org
-
gemad＠outlook.com -
Milosz Wasilewski -
Remi Duraffort