Add tag include and exclude options

[MofX]

This works the same way as --include and --exclude of the
robot command line utility.
It can be used for example for filtering out skipped tests,
that were marked with a specific tag

Signed-off-by: Joerg Vehlow joerg.vehlow@aox-tech.de

I am willing to add unit tests as well, if this PR gets attention

[Tattoo]

Hi,

Thanks for contributing!

Could you illuminate me a bit about what is the intended use case for this feature? Refining the RF log/report that the plugin then publishes is already directly built-in in Robot's rebot tool.

What does this functionality in the plugin add to that?

[MofX]

As I already described in the commit message, it can be used to exclude skipped tests. If there are different reasons for skipping tests, it could be required for the output.xml to still contain all tests, including skipped ones, for later analysis. That is actually the use case, this pr is designed to solve.

I could imagine, there are also other use cases, like leaving known failing tests or tests drafts out of the statistics while still keeping them in the log for analysis.

[Tattoo]

So it just replicates functionality in Robot Framework itself (as I previously linked)?

[MofX]

Yes, but it moves the responsibility where it belongs. If the visualized data should be reduced only in jenkins, it should be part of the plugin and not any preprocessing step.

If it was done in preprocessing, the full results are not available anymore (or require another archived file). So there is a big difference between preprocessing and doing it in jenkins

[Tattoo]

I would encourage you to reread what rebot does. It is specifically about post-processing log/report to different versions of log/report with quite extensive possibilities. I do not agree that we should just duplicate this existing functionality as it is code we have to maintain in the future.

I feel this plugin's core tenent is to provide functionality that adds to Robot Framework's.

[MofX]

I do know, that it can be done using rebot. It is just inconvenient to do it using rebot in some cases.

Imagine a more complicate use case, where jenkins does not do the build itself and maybe even has no access to rebot.

[MofX]

BTW I am not the first one with this requirement. See https://issues.jenkins-ci.org/browse/JENKINS-8378

[Tanarri]

I appreciate this pr. Would be really helpful.