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

Tooling Should Exist To Evaluate Assumption of No Unit Test Dependency #4

Open
aolszowka opened this issue Aug 20, 2020 · 0 comments
Open

Comments

@aolszowka
Copy link
Owner

In the README.md one of the assumptions of this tool is:

In addition no project should "depend" on a Unit Test project which means that its unlikely to be blocking any project.

We should have some tooling to try and test this assumption. My first thought would be to use https://github.com/aolszowka/MsBuildProjectReferenceDependencyGraph to look at the dependencies of a project. However that tool, as currently written, only supports looking at ProjectReferences and makes no account for what type of project is being referenced.

We need something that behaves like MsBuildProjectReferenceDependencyGraph but also goes one further in attempting to determine if any of the N-Order Dependencies also reference the NUnit.MSBuild package which would indicate a place where this assumption is broken.

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

No branches or pull requests

1 participant