Highlight for in tests #505
Open
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
|
Also looks good. I wonder if we could add |
|
The trouble with this one is that the tests pass when they shouldn't (because the compare file doesn't have any annotations in it yet). Therefore, the annotations are not being picked up by the underlying testHighlighting. I posted this mostly to find out if anybody else [was interested and] had any other ideas about how to test colorization. |
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.
Accompaniment for #504.
Tests for highlighting the "in" keyword in a for statement. The test passes, but it should be failing: The color annotations are not being picked up by the annotator test functions in CodeInsightTestFixture. I've posted this test so that a)somebody else can take a look and tell me what I'm missing; b) I can remember that I have to revisit this issue.