You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Vladimir Sitnikov (Jira)" <ji...@apache.org> on 2019/11/13 09:15:00 UTC

[jira] [Reopened] (CALCITE-2457) Upgrade to JUnit 5

     [ https://issues.apache.org/jira/browse/CALCITE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Sitnikov reopened CALCITE-2457:
----------------------------------------
      Assignee: Vladimir Sitnikov  (was: Andrei Sereda)

{quote} Does it mean we can use JUnit5 functionality now ? {quote}
Not really.

I closed the issue to clarify that there's nothing to do here.
Ok, no problem for me to keeping it open, I just wanted to avoid duplicating the efforts.

> Upgrade to JUnit 5
> ------------------
>
>                 Key: CALCITE-2457
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2457
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Vladimir Sitnikov
>            Assignee: Vladimir Sitnikov
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: assert_equals.png, truth_assertmap.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> JUnit 5 brings multiple useful features so tests are easier to read and write.
> Is there something that blocks upgrading to JUnit 5?
> By upgrade I mean bumping up the dependency version and creating new tests with JUnit 5 features.
> Relevant features of JUnit 5: dynamic test, nested tests, parameterized tests
> https://twitter.com/nipafx/status/1027095088059559936



--
This message was sent by Atlassian Jira
(v8.3.4#803005)