Quantcast

[jira] [Commented] (GROOVY-8159) Make assert output easy to parse

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (GROOVY-8159) Make assert output easy to parse

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/GROOVY-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971125#comment-15971125 ]

Daniil Ovchinnikov commented on GROOVY-8159:
--------------------------------------------

This:
bq. to recognize in the compiler we do an assert with == and then call an assert function, which would produce a slightly different exception
It doesn't have to be rendered in some another way. Just store two additional fields with some data for binary expressions  with == operator.


> Make assert output easy to parse
> --------------------------------
>
>                 Key: GROOVY-8159
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8159
>             Project: Groovy
>          Issue Type: Improvement
>          Components: groovy-runtime
>    Affects Versions: 2.4.10
>            Reporter: Iurii
>         Attachments: 1 contains assert.jpg, 2 contains equals.jpg
>
>
> Based on https://youtrack.jetbrains.com/issue/IDEA-171275
> IntelliJ IDEA provides great feature: "Click to see difference" in test console.
> It's very useful because it opens comparison windows where differences are highlighted.
> It's supported for JUnit assertXXX but not for Groovy assert because: "JUnit's ComparisonFailure contains all necessary data which can be rendered later while Groovy's PowerAssertionError contains already rendered message which is hard to parse (if it's even possible)"
> Can assert output be improved so that IDE can parse it?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Loading...