Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add example junit test to archetype extensions-jvm #907

Merged
merged 1 commit into from
Dec 31, 2022
Merged

Add example junit test to archetype extensions-jvm #907

merged 1 commit into from
Dec 31, 2022

Conversation

obermeier
Copy link
Member

Purpose

To reduce effort to write unit tests for new processors.
Do you prefere JUnit 4 ?

Remarks

PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no

@tenthe
Copy link
Contributor

tenthe commented Dec 28, 2022

Hey @obermeier,
Currently JUnit 4 is used, but there is already an issue to migrate to JUnit 5 (#782).
In some tests we still rely on Powermock, once this is removed we can upgrade.

@bossenti bossenti added this to the 1.0.0 milestone Dec 28, 2022
@bossenti bossenti added testing Relates to any kind of test (unit test, integration, or E2E test). java Pull requests that update Java code labels Dec 28, 2022
@bossenti bossenti merged commit e33f042 into apache:dev Dec 31, 2022
@bossenti bossenti modified the milestones: 1.0.0, 0.91.0 Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
java Pull requests that update Java code testing Relates to any kind of test (unit test, integration, or E2E test).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants