Vincent
Vincent
Currently, the filtering options in hiptest-publisher do not work with test runs (except for the filter-on-status one). This could be helpful, for example to enable parallel executions in CI pipelines.
Most people starting with Hiptest-publisher use the "as a service" version that's inside Hiptest and have a configuration file named "hiptest-publisher.conf" available. The idea would be that, if the -c|--config-file...
It will display empty lines only when trying to produce the created action words for example.
For traceability reasons, it can be interesting, from the test code, to have a link to the scenario in Hiptest.
Currently, the options to handle privacy are based on an exclusion list. This does not work fine for our use-case. The idea behind this pull request is to anonymize everything...