Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@latkin
Copy link
Contributor

@latkin latkin commented Jun 2, 2015

Various fixes to address bitrot in the tests - uncovered these as I am getting our internal test infrastructure running again.

  • Older NUnit used internally compares collections differently
    • Has trouble with nested collections
    • Enforces that empty collections have the same type (newer NUnit is lax about this)
  • Add NoMT test tag to various new tests that don't support mixed .NET version testing (i.e. .NET 2/4 multitargeting)
  • Make sure all IDE bits build with correct versions of VS SDK dependencies
    • IDE unit tests were all failing for me with latest VS RC installed
  • Various small tweaks to account for versioning and file paths used by VS

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure we want this? The reporting will be worse if something breaks.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not perfect, no. Failures will still have a stack pointing to the line that failed, though, so it's not too bad. And FWIW this is the pattern used for most of the tests already (due to the same reason, that older NUnit has broken AreEqual for complicated collections).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rewriting tests in such a way because of an old test framework dependency, feels really like a bad idea.

@latkin latkin closed this in 275b832 Jun 3, 2015
@latkin latkin added the fixed label Jun 3, 2015
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.

3 participants