Wildcard support for test result files

[Autom8edChaos]

Wildcards can be used for testresult files like:
C:\results*.trx
or
C:\runs\Acceptance*.xml;C:\dev\unit*.xml

Works in combination with semicolon.
Multiple files are selected as wildcard matches more than one files.

All tests pass, new tests added.
Commandline use tested in the wild.

Code is implemented for commandline, powershell, msbuild and for future use in UI*. All other behaviour in these configs is kept the same (like: semicolon use is only implemented for commandline).

* UI does a check on the existing of the file before the GENERATE button becomes enabled. This does not work wild wild cards.

Known Limitations:

• does not work when path is empty
• unknown if relative paths are supported
• breaks when path does not exist

Above limited behaviour is not described or tested in the master version, please advice.

[dirkrombauts]

Thank you for your contribution!

Would you be willing to expand your work - for example I would be grateful if you could address the limitations that you discovered in the existing code.

Also: as you discovered the usage of semicolons isn't uniform. It would be great if you could make this more general.

[Autom8edChaos]

I can look into it and create testcases for relative and UNC paths. Difficulty is that I experienced the filesystem mock a bit limited to do this, but maybe I have not read enough into it. Otherwise I need to setup some tests on a real filesystem, but can be brittle on other users system because different setups.

Questions:

• What should be the behaviour when a path is empty or does not exist: Gracefully exit with message, throw exception or silently go on without using that/a resultfile?
• Semicolon limitations is what I thought was by design, but it should be easy to implement. Just implement it?

I'll take a look into the UI behaviour for feasibility.

[dirkrombauts]

Hi,

• Exit behaviour: to be hones I'm not sure how Pickles behaves right now if you supply one result file and it doesn't exist. I think the optimal behaviour would be to exit with an error code and a message.
• Semicolons: I'm not sure how to provide multiple result files in the MSBuild runner. That's why I didn't implement it yet. Do you have any ideas? Providing them in the GUI isn't too difficult in principle but it involves adding a listbox, and ways to edit the content of the listbox.

[Autom8edChaos]

Improved the handling of wildcard support and semicolons by adding them to the MSBuild and UI parts. The UI still needs a solution on the front end, but it is already implemented on the back end.

When there are multiple matches on the same file (like C:\foo*.trx;C:*bar.trx matches twice on C:\foobar.trx) it is rendered into a single match.

When there are no matches, no error is thrown in the file-collection functions. This is the same behaviour as before.

Unfortunately, I checked in too many files (some config and test result files), is there a way you can ignore this?

[dirkrombauts]

Thanks for your continuing efforts.

About the files. There's some merge conflict on the build server ... I think the best thing would be for you to rebase on develop and reapply your changes ...

[Autom8edChaos]

Closing this request, I am messing up with my GitHub settings. Will do a new pull request.