Moar test coverage #65
Merged
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
6 tasks
asgrim
force-pushed
the
moar-test-coverage
branch
from
1a22514
to
60439f1
Compare
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.
Merging this will resolve #24
Note that the coverage for
ReflectionClassis already improved in #59The stuff that means it's not 100% quite yet is:
Reflectionfolder so is already accounted forReflector\Genericthat somehow is not covered and I'm not sure why (see http://s.asgrim.com/1034bf.png)NodeCompilerthis will be fixed by issue CompileNodeToValue does not evaluate the value of constant expressions #19 so is already accounted for