Open bt-jagababu opened 4 months ago
But you already can do that when test run is created and labels assigned? Do you want it to be a default behaviour?
@bt-jagababu you can actually set labels during a run and filter by labels after this
https://docs.testomat.io/reference/reporter/pipes/testomatio.html#assign-label-to-run
To assign a label to run, a label with scope runs must exist. Then a label can be passed via TESTOMATIO_LABEL variable:
TESTOMATIO={API_KEY} TESTOMATIO_LABEL=release <actual run command>
There is a way to pass a value to label via:
TESTOMATIO={API_KEY} TESTOMATIO_LABEL="module:checkout" <actual run command>
Or you can set multiple labels separating them with comma
TESTOMATIO={API_KEY} TESTOMATIO_LABEL="release,module:checkout" <actual run command>
Thanks for the suggestions @poliarush, @tikolakin and @TetianaKhomenko .
I have tried using the Labels the way you suggested. The labels have been tagged in the Test run but the values are not added in the filter list. Hence there is no way for me to filter it. Please see the screenshot. Please let me know if there is a workaround for the same.
Hi @bt-jagababu , you should make labels available in filters
Hi @tikolakin , Yes its already done. The problem is the branch values are runtime generated that needs to get updated in the filter values.
@poliarush I agree we should label this automatically from our reporter I already thought about it, we should take this into the next sprint
well, I am quite happy not to have a branch name assigned automatically and have it as a new default behaviour. Quite often, a test code branch name isn't as important as a branch of an application under test I think what @bt-jagababu is trying to address here is that labels on FE are not showing values provided from reported (cli args)
Is your feature request related to a problem? Please describe. I'm always frustrated when I can't differentiate a run from a stable branch or feature branch.
Describe the solution you'd like