groovy / groovy/groovy-eclipse
Add support for Compare Result command in JUnit view for Groovy assert comparisons
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
When a JUnit test case uses Assert.assertEquals, a test failure displays the option Compare Result in the JUnit view's context menu (see below) for easy comparison of expected and actual strings. If possible, enhance this capability to support Groovy's assert keyword (at least for == comparisons).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a JUnit failure from a Groovy assert using ==, then compare its JUnit view context menu with a failure from Assert.assertEquals. Done means Groovy string comparisons expose the Compare Result command for expected-versus-actual inspection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- devtools, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100