chore: tests migration to assertj (KotlinStdlibCompatUtilsTest, ModelAutolinkingDependenciesJsonTest, PathUtilsTest, DependencyUtilsTest, ProjectUtilsTest)

[kachmashk]

Summary:

#45596

Changelog:

Migrated to AssertJ within files:

• KotlinStdlibCompatUtilsTest.kt,
• ModelAutolinkingDependenciesJsonTest.kt,
• PathUtilsTest.kt,
• DependencyUtilsTest.kt,
• ProjectUtilsTest.kt.

[INTERNAL] [CHANGED] - Migrated KotlinStdlibCompatUtilsTest, ModelAutolinkingDependenciesJsonTest, PathUtilsTest, DependencyUtilsTest, ProjectUtilsTest from junit.Assert to assertj.core.api.Assertions.

Test Plan

[facebook-github-bot]

Hi @kachmashk!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[react-native-bot]

	Warnings
⚠️	📋 Missing Test Plan - Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.

Generated by 🚫 dangerJS against e9f806b

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[react-native-bot]

	Warnings
⚠️	📋 Missing Test Plan - Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.

Generated by 🚫 dangerJS against e9f806b

[kachmashk]

Hey @cortinico, cannot add you as a reviewer so @ you here.

[cortinico]

Can you invert the equal assertion so that is:

assertThat(actual).isEqualTo(expected)

You have this in several tests

[cortinico]

Can you invert the equal assertion so that is:

assertThat(actual).isEqualTo(expected)

You have this in several tests

[kachmashk]

Can you invert the equal assertion so that is:

assertThat(actual).isEqualTo(expected)

You have this in several tests

Made a mistake by not checking assertEquals documentation where expected is a first argument, not second like I assumed. Reverted actual with expected within the isEqualTo.

[facebook-github-bot]

@cortinico has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[kachmashk]

Hey @cortinico, how could I fix the Facebook Internal - Linter? I cannot see what went wrong as it's only for Meta's employees.

[cortinico]

Hey @cortinico, how could I fix the Facebook Internal - Linter? I cannot see what went wrong as it's only for Meta's employees.

I fixed it for you. The status doesn't update automatically, but the final commit that will land will be properly formatted 👍

[facebook-github-bot]

@cortinico merged this pull request in 4cc46e3.

[react-native-bot]

This pull request was successfully merged by @kachmashk in 4cc46e3

^{When will my fix make it into a release? | How to file a pick request?}