Test definition names need to be unique -> really?
When I submit a job with two test actions of the same name, the following error occurs:
error_type: Job case: job error_msg: Invalid job data: ['Test definition names need to be unique.', 'Test definition names need to be unique.'] result: fail definition: lava
Is this really a necessary constraint? LAVA prepends a number to each test action, "myfirsttest" becomes "0_myfirsttest", "mysecondtest" becomes "1_mysecondtest". Why can't I have "0_mytest" and "1_mytest"?
I would like to group test results by the name of their test suites, that's why I am asking. I have several test cases, which belong semantically together, scattered over different test actions.