Feature/#41 - Updated NUnit tests to use new NUnit pattern #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AtwoodTM
changed the title
|
The PR was submitted two weeks ago with no response. Is this project still alive @jbtule? If not, we will use our fork to progress development for FSharp.Interop.Dynamic. |
|
It's still alive in that it's critical to our business, but not really under active development for new features. With reformatting of every file, this PR involves a lot more scrutiny than a PR described as updating the unit tests asset method. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The NUnit tests had been using the deprecated Assert.AreEqual. These have been changed to the new Assert.That pattern....