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

Adding fork of xunit.console #1627

Merged
merged 16 commits into from
Jan 18, 2019
Merged

Conversation

josalem
Copy link
Contributor

@josalem josalem commented Dec 19, 2018

This PR adds a fork of the xunit console runner (v2.4.1) to Arcade. The console runner for v2 of xunit is no longer being maintained, so this will provide a centralized source for long term maintenance and feature addition until a more viable solution, e.g., a backwards-compatible v3 of xunit, comes along.

The source code under src/Microsoft.DotNet.XUnitConsoleRunner generates a xunit.console.netcore.dll that can be used in the same way as the xunit.console.runner nuget package's xunit.console.dll.

#1613

@BruceForstall
Copy link
Member

@josalem Is this ready to go, modulo reviews?

@ViktorHofer ping

@josalem
Copy link
Contributor Author

josalem commented Jan 9, 2019

As far as I'm aware, this should be good to go sans any issues brought up by review. My understanding is that Arcade's build should handle turning this into a nupkg available on the blob feed, so all that's left is reviewing the changes.

@sergiy-k
Copy link

@ViktorHofer, @markwilkie, is there anything specific that needs to be done before this PR can be accepted? Thank you!

@ViktorHofer
Copy link
Member

Thanks. I'll review the PR later today.

@ViktorHofer
Copy link
Member

Quick question, why does it generate a xunit.console.netcore.dll and not a xunit.console.dll? I would expect the latter.

@josalem
Copy link
Contributor Author

josalem commented Jan 15, 2019

I modified the name to differentiate from the official XUnit console runner they still have hosted on NuGet. Mainly so we are not publishing a package with the same name and being construed as the official XUnit console runner. It's a superficial change, so it would be trivial to change it back.

@ViktorHofer
Copy link
Member

I would prefer if we keep the official assembly name and only change the package name.

@ViktorHofer
Copy link
Member

Looking now...

@ViktorHofer
Copy link
Member

Do we really need the netcoreapp1.0 build configuration?

@ViktorHofer
Copy link
Member

ViktorHofer commented Jan 17, 2019

@josalem I removed other unused code (+ partially remaining netfx ifdefs). We are still adding 5.5k lines to arcade which is the bare minimum as I believe. I'm now experimenting if I can combine the Microsoft.DotNet.XUnitRunnerUap with this package.

John Salem added 12 commits January 18, 2019 18:12
* Had to comment out xunit assembly names since it looks like Arcade adds its own
* Replaced project references with the appropriate package references
…ense:

* Modified name of assembly to xunit.console.netcore to differentiate from xunit.console NuGet pacakge
* moved source into Microsoft.DotNet.XUnitConsoleRunner
* Added attributions to README for project dir
@ViktorHofer
Copy link
Member

I'm done with the required work. We are now using the sources here for different variations of the runner (netcoreapp2.0, uap, uapaot), I'm very happy about that. Tested locally and everything works as expected.

@ViktorHofer
Copy link
Member

Thanks a lot @josalem for your work!

@sergiy-k
Copy link

@ViktorHofer, @josalem, thank you so much!

@BruceForstall
Copy link
Member

Are we now using this for corefx test runs (and others)?

cc @echesakovMSFT

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.

4 participants