Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Expecto's new --log-name parameter #60

Merged
merged 1 commit into from
Mar 6, 2018

Conversation

rmunn
Copy link
Contributor

@rmunn rmunn commented Mar 6, 2018

This fixes #59 by bumping the required Expecto version to 6.0.0 (in order to use the --log-name parameter) and dotnet-mono to 0.5.1 (so that its syntax will match the dotnet run syntax, with a bare -- parameter separating dotnet-mono params from params intended for the program being run).

Note that I have only tested this on one Linux machine so far, so it might be good to try this PR on at least a couple more machines before merging it and pushing a new version of the template.

Log messages will now make it obvious which framework (core, net461...)
was running the tests when that log message was produced.
@TheAngryByrd
Copy link
Owner

Works on MacOS, I'll publish a beta

@TheAngryByrd TheAngryByrd merged commit 4f3ebd7 into TheAngryByrd:master Mar 6, 2018
TheAngryByrd pushed a commit that referenced this pull request Mar 6, 2018
* FEATURE: Use expecto's --log-name to specify targetframework when running tests.  Bumps Expecto to 6.0.0 and dotnet-mono to 0.5.1. (#60)
TheAngryByrd pushed a commit that referenced this pull request Mar 7, 2018
* FEATURE: Use expecto's --log-name to specify targetframework when running tests.  Bumps Expecto to 6.0.0 and dotnet-mono to 0.5.1. (#60)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Request: different Expecto log names for each target framework (needs a new feature in Expecto)
2 participants