--loggerOutput option

[TheRealPiotrP]

Of course, the name is just a suggestion

Users should be able to specify the output path for loggers. This would allow aggregating all logs in one artifact folder. This, in turn, makes it much easier to scan logs for failures.

/cc @blackdwarf @livarcocc

[codito]

Elaborating bit more to clarify expectation. Thoughts?

• User will specify the directory for all result logs or should she specify the result file name. I prefer later for automation friendliness :)
• If user has 2 target frameworks, the results are merged in the same trx
• If user specifies multiple test projects, the results are merged in the same trx

/cc @pvlakshm

[TheRealPiotrP]

That sounds great. If I want to avoid merging I can do smaller invocations. Makes sense!

[pvlakshm]

Triage:

• User will specify the filename using /logger:"trx;logfile=<filename>"
• If user has 2 target frameworks, each will be a separate .trx file. If we can figure out that the targets involved, then the targetname will be appended to the filename specified. If we cannot figure out the targetname, then we will append (1), (2) etc. to the filename specified.
• If user specifies multiple test projects, then trx file(s) generated by subsequent csproj's will clobber those already created. If any of the csprojs is targeting mulitple frameworks, we will use the above semantics to disambiguate.

[smadala]

• Fixed in fc1f7b9
• User can specify file name using logfilename parameter, trx file will be create in test results directory.
• Test results directory can be specified as first class argument once dotnet test should accept an argument to overwrite testresults folder #299 resolved.