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

Remove Mojo test cases #4230

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Sep 9, 2024

Tycho currently contains some so called "Mojo Testcases" that are ones that (partly) simulate the execution of a mojo, but these have some problems:

  1. They currently depend on heavy outdated (and deprecated) maven-plugin-testharness
  2. They often do not have a full test setup so we need to have some quirks in the code (e.g components are null)
  3. They are often hard to understand as they are a mixture of (incomplete) maven setups with things setup in the code 4) We even have some constructors only used to support these cases 5) As they often test very specific internal behavior they often need adjustments.
  4. For the Maven 4 transition one needs to adjust them to new maven4 api and components and executions.

On the other hand we have a very good integration suite that is made of actual executable examples and test, changing internal implementation details does not affect these or show clear use-cases that break.

Because of this and to prepare for the Maven 4 transition these tests are now deleted.

@akurtakov any objections?

Tycho currently contains some so called "Mojo Testcases" that are ones
that (partly) simulate the execution of a mojo, but these have some
problems:

1) They currently depend on heavy outdated (and deprecated)
maven-plugin-testharness
2) They often do not have a full test setup so we need to have some
quirks in the code (e.g components are null)
3) They are often hard to understand as they are a mixture of
(incomplete) maven setups with things setup in the code
4) We even have some constructors only used to support these cases
5) As they often test very specific internal behavior they often need
adjustments.
6) For the Maven 4 transition one needs to adjust them to new maven4 api
and components and executions.

On the other hand we have a very good integration suite that is made of
actual executable examples and test, changing internal implementation
details does not affect these or show clear use-cases that break.

Because of this and to prepare for the Maven 4 transition these tests
are now deleted.
@laeubi laeubi added this to the 5.0 milestone Sep 9, 2024
@akurtakov
Copy link
Member

If you believe that what these test is covered by integration tests - go for it, otherwise we risk breaking functionality later on if no test cover it anymore.

Copy link

github-actions bot commented Sep 9, 2024

Test Results

  600 files  ±0    600 suites  ±0   4h 16m 26s ⏱️ + 11m 43s
  429 tests ±0    422 ✅ ±0   7 💤 ±0  0 ❌ ±0 
1 287 runs  ±0  1 265 ✅ ±0  22 💤 ±0  0 ❌ ±0 

Results for commit 835ad85. ± Comparison against base commit 9b3eb9f.

@laeubi laeubi merged commit 41e8574 into eclipse-tycho:main Sep 10, 2024
10 of 11 checks passed
@laeubi laeubi mentioned this pull request Sep 12, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants