Skip to content

Use AssertJ assertions in tests #51

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

Merged
merged 2 commits into from
Aug 2, 2024
Merged

Conversation

ebyhr
Copy link
Contributor

@ebyhr ebyhr commented Aug 1, 2024

Description

PolarisObjectMapperUtilTest already uses AssertJ.
AssertJ provides more helpful messages than JUnit when failed.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • Firmware version:
  • Hardware:
  • Toolchain:
  • SDK:

Checklist:

Please delete options that are not relevant.

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue
  • I have signed and submitted the ICLA and if needed, the CCLA. See Contributing for details.

@ebyhr ebyhr force-pushed the ebi/assertj-test branch from 8192bd0 to 92d83bf Compare August 1, 2024 13:59
@ebyhr ebyhr changed the title Use AssertJ assertions in ResolverTest Use AssertJ assertions in tests Aug 1, 2024
@ebyhr ebyhr requested a review from a team as a code owner August 1, 2024 22:21
Copy link
Contributor

@flyrain flyrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@annafil annafil merged commit 5c78eef into apache:main Aug 2, 2024
3 checks passed
@ebyhr ebyhr deleted the ebi/assertj-test branch August 2, 2024 04:01
fivetran-kostaszoumpatianos pushed a commit to fivetran/polaris that referenced this pull request Jun 18, 2025
…pache#51)

* Gradle wrapper download / macOS

Fixes apache#49

* Also fix apache#50

* shasum + sha256sum
fabio-rizzo-01 pushed a commit to fabio-rizzo-01/polaris that referenced this pull request Jun 20, 2025
# This is the 1st commit message:

 apache#772 fixed integration tests and synched with main

Mypy did a new release 1.16.1 and it cause our CI to fail for about 20 minutes due to missing wheel (upload not completed)
```
 | Unable to find installation candidates for mypy (1.16.1)
    |
    | This is likely not a Poetry issue.
    |
    |   - 14 candidate(s) were identified for the package
    |   - 14 wheel(s) were skipped as your project's environment does not support the identified abi tags
    |
    | Solutions:
    | Make sure the lockfile is up-to-date. You can try one of the following;
    |
    |     1. Regenerate lockfile: poetry lock --no-cache --regenerate
    |     2. Update package     : poetry update --no-cache mypy
    |
    | If neither works, please first check to verify that the mypy has published wheels available from your configured source that are compatible with your environment- ie. operating system, architecture (x86_64, arm64 etc.), python interpreter.
    |

```
This PR temporarily restrict the mypy version to avoid the similar issue.

We may consider bring poetry.lock back to git tracking so we won't automatically update test dependencies all the time

# This is the commit message apache#48:

Remove `.github/CODEOWNERS` (apache#1902)

As per this [dev-ML discussion](https://lists.apache.org/thread/jjr5w3hslk755yvxy8b3z45c7094cxdn)
# This is the commit message apache#49:

Rename quarkus as runtime (apache#1695)

# This is the commit message apache#50:

parent 3185adf
author Mend Renovate <bot@renovateapp.com> 1749165686 +0200
committer Rizzo Cascio, Fabio <fabio.rizzocascio@jpmorgan.com> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

# This is the commit message apache#51:

Mutable objects used for immutable values apache#772: fixed integration tests

# This is the commit message apache#52:

parent 3185adf
author Mend Renovate <bot@renovateapp.com> 1749165686 +0200
committer Rizzo Cascio, Fabio <fabio.rizzocascio@jpmorgan.com> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

Mutable objects used for immutable values apache#772: added final to base and core fields

Mutable objects used for immutable values apache#772: fixed tests
travis-bowen pushed a commit to travis-bowen/polaris that referenced this pull request Jun 20, 2025
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.

3 participants