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

ASF subversion and git services commented on AVRO-3628:
-------------------------------------------------------

Commit 65c3ac3354fceaaa6aaa2e81bf54475b1541b2b1 in avro's branch 
refs/heads/avro-3628-junit-5.x-vintage from Martin Tzvetanov Grigorov
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=65c3ac335 ]

AVRO-3628: Migrate avro-service-archetype tests to JUnit 5.x

Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>


> [Java] JUnit 4.x tests are not executed
> ---------------------------------------
>
>                 Key: AVRO-3628
>                 URL: https://issues.apache.org/jira/browse/AVRO-3628
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.11.1
>            Reporter: Martin Tzvetanov Grigorov
>            Assignee: Martin Tzvetanov Grigorov
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> AVRO-3579 introduced JUnit 5 and migrated some of the tests.
> This confused maven-surefire-plugin and now it does not run the JUnit 4.x 
> tests, e.g.:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M7:test (default-test) @ 
> avro-maven-plugin ---
> [INFO] Tests will run in random order. To reproduce ordering use flag 
> -Dsurefire.runOrder.random.seed=71852499748477
> [INFO] Using auto detected provider 
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO] 
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> [INFO] --- maven-checkstyle-plugin:3.1.2:check (checkstyle-check) @ 
> avro-maven-plugin ---
> [INFO] Starting audit...
>  {code}
>  
> We should use JUnit 5.x Vintage engine instead of JUnit 4.x



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to