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

Migrate test setup to JUnit 5 (Jupiter) #782

Closed
5 tasks done
dominikriemer opened this issue Nov 26, 2022 · 0 comments · Fixed by #2536
Closed
5 tasks done

Migrate test setup to JUnit 5 (Jupiter) #782

dominikriemer opened this issue Nov 26, 2022 · 0 comments · Fixed by #2536
Labels
enhancement New feature or request migrated from jira Indicates that a issue has been migrated from JIRA (only automatically assigned - Do not modify!) testing Relates to any kind of test (unit test, integration, or E2E test).
Milestone

Comments

@dominikriemer
Copy link
Member

dominikriemer commented Nov 26, 2022

Description

This issue collects the individual steps that need to be taken to migrate from JUnit4 to JUnit5.

Steps

Old Issue description

  • Replace Powermock either with Mockito's mockStatic or completely eliminate static methods for testing

Imported from Jira STREAMPIPES-592. Original Jira may contain additional context.
Reported by: bossenti.

@dominikriemer dominikriemer added improvement migrated from jira Indicates that a issue has been migrated from JIRA (only automatically assigned - Do not modify!) labels Nov 26, 2022
@bossenti bossenti added enhancement New feature or request and removed improvement labels Nov 27, 2022
@bossenti bossenti added this to the 1.0.0 milestone Nov 27, 2022
@bossenti bossenti added the testing Relates to any kind of test (unit test, integration, or E2E test). label Nov 28, 2022
@bossenti bossenti modified the milestones: 1.0.0, post-1.0 May 5, 2023
@tenthe tenthe linked a pull request Mar 12, 2024 that will close this issue
tenthe added a commit that referenced this issue Mar 13, 2024
* refactor(#2518): Update junit4 to junit5 in dependencies with  junit-vintage-engine (#2519)

* refactor(#2518): Update junit4 to junit5 in dependencies with  junit-vintage-engine

* Update streampipes-commons/src/test/java/org/apache/streampipes/commons/resources/TestResources.java

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>

---------

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>

* refactor(#2525): Update JUnit4 to JUnit 5 syntax in modules (#2526)

* refactor(#2518): Update junit4 to junit5 in dependencies with  junit-vintage-engine (#2519)

* refactor(#2518): Update junit4 to junit5 in dependencies with  junit-vintage-engine

* Update streampipes-commons/src/test/java/org/apache/streampipes/commons/resources/TestResources.java

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>

---------

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>

* refactor(#2525): Update JUnit4 to JUnit 5 syntax in modules
- streampipes-client
- streampipes-client-api
- streampipes-commons
- streampipes-connect-management
- streampipes-connect-shared
- streampipes-data-explorer

* 2525 migrate all tests to junit5 syntax to remove junit vintage engine 2 (#2530)

* refactor(#2525): Update JUnit4 to JUnit 5 for the main modules

* 2525 migrate all tests to junit5 syntax to remove junit vintage engine 3 (#2531)

* refactor(#2525): Update JUnit4 to JUnit 5 for the extensions modules

* refactor(#2525): Remove junit-vintage-engine

* refactor(#2525): Remove powermock (#2532)

* refactor(#2525): Remove powermock

* refactor(#2525): Remove rest-assured

* refactor(#2525): Remove wire-mock

* refactor(#2525): Refactor TestBooleanFilterProcessor (#2534)

---------

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>

---------

Co-authored-by: Tim <50115603+bossenti@users.noreply.github.com>
@bossenti bossenti modified the milestones: post-1.0, 0.95.0 May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request migrated from jira Indicates that a issue has been migrated from JIRA (only automatically assigned - Do not modify!) testing Relates to any kind of test (unit test, integration, or E2E test).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants