The voting time of migrating to JUnit 5[1] has passed. I'd like to close
the vote now.
There were three +1 binding votes:
- Arvid Heise (binding)
- Chesnay Schepler (binding)
- Roman Khachatryan (binding)
There were no -1 votes.
The migration plan has been accepted. Thanks everyone for your supp
+1 (binding)
Regards,
Roman
On Mon, Jul 5, 2021 at 9:47 AM Chesnay Schepler wrote:
>
> +1 (binding)
>
> On 05/07/2021 09:45, Arvid Heise wrote:
> > +1 (binding)
> >
> > On Wed, Jun 30, 2021 at 5:56 PM Qingsheng Ren wrote:
> >
> >> Dear devs,
> >>
> >>
> >> As discussed in the thread[1], I’d lik
+1 (binding)
On 05/07/2021 09:45, Arvid Heise wrote:
+1 (binding)
On Wed, Jun 30, 2021 at 5:56 PM Qingsheng Ren wrote:
Dear devs,
As discussed in the thread[1], I’d like to start a vote on migrating the
test framework of Flink project to JUnit 5.
JUnit 5[2] provides many exciting new fea
+1 (binding)
On Wed, Jun 30, 2021 at 5:56 PM Qingsheng Ren wrote:
> Dear devs,
>
>
> As discussed in the thread[1], I’d like to start a vote on migrating the
> test framework of Flink project to JUnit 5.
>
>
> JUnit 5[2] provides many exciting new features that can simplify the
> development of
Dear devs,
As discussed in the thread[1], I’d like to start a vote on migrating the
test framework of Flink project to JUnit 5.
JUnit 5[2] provides many exciting new features that can simplify the
development of test cases and make our test structure cleaner, such as
pluggable extension models
