Add Scala.js handling of @Test annotations with arguments #7462
Conversation
This file contains hidden or 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
dottybot
reviewed
Oct 28, 2019
There was a problem hiding this comment.
Hello, and thank you for opening this PR! 🎉
All contributors have signed the CLA, thank you! ❤️
Commit Messages
We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).
Please stick to these guidelines for commit messages:
- Separate subject from body with a blank line
- When fixing an issue, start your commit message with
Fix #<ISSUE-NBR>:- Limit the subject line to 72 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line ("Add" instead of "Added")
- Wrap the body at 80 characters
- Use the body to explain what and why vs. how
adapted from https://chris.beams.io/posts/git-commit
Have an awesome day! ☀️
|
Notably, I'm not sure this one is quite there yet - I want to improve the pattern matching so as to match only the actual |
Lacaranian
force-pushed
the
additional-sjs-tests
branch
from
54e49a2 to
ea755e2
Compare
Lacaranian
changed the title
Partial fix for lampepfl#7113 To be able to use the `expected` and `timeout` annotation arguments in JUnit @test annotations, add handling for these arguments by supplying them as arguments to the resolved constructor for the JUnit test class. Enable the JUnitAnnotationsParamTest, which depends on this functionality.
Lacaranian
force-pushed
the
additional-sjs-tests
branch
from
ea755e2 to
78e9a02
Compare
|
The latest version of this is now in a reviewable state, though quite possibly still in need of some changes. |
sjrd
approved these changes
Nov 4, 2019
smarter
approved these changes
Dec 5, 2019
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.
To be able to use the
expectedandtimeoutannotation arguments inJUnit @test annotations, add handling for these arguments by supplying
them as arguments to the resolved constructor for the JUnit test class.
Enable the JUnitAnnotationsParamTest, which depends on this
functionality.