8000 breaking(tests): mutation responses are now sparse by cmgrote · Pull Request #2316 · atlanhq/atlan-java · GitHub
[go: up one dir, main page]

Skip to content

breaking(tests): mutation responses are now sparse#2316

Merged
cmgrote merged 2 commits intomainfrom
dependencies
Mar 12, 2026
Merged

breaking(tests): mutation responses are now sparse#2316
cmgrote merged 2 commits intomainfrom
dependencies

Conversation

@cmgrote
Copy link
Collaborator
@cmgrote cmgrote commented Mar 12, 2026

Summary

The Atlan backend API changed such that mutation responses (e.g. removeCertificate(), removeAnnouncement()) are now sparse — they only return fields directly related to the specific mutation. Previously, a removeCertificate() call would return the full asset state including announcement fields; it no longer does.

This PR refactors all affected integration tests to call .get() on the asset by GUID immediately after each mutation, asserting against the actual server state rather than the now-incomplete mutation response.

Affected test classes (16): ADLSAssetTest, APIAssetTest, AirflowAssetTest, AnaplanAssetTest, AppAssetTest, AzureEventHubTest, CubeTest, DataStudioAssetTest, FileTest, GCSAssetTest, GlossaryTest, InsightsTest, KafkaTest, PresetAssetTest, S3AssetTest, SupersetAssetTest

Also includes:

  • Throttled integration test parallelism in CI to reduce server overload
  • Dependency version updates (gradle/libs.versions.toml)
  • Java SDK model sync from atlanhq/models

Test plan

  • Integration tests pass with updated assertion pattern (./gradlew test -PintegrationTests)
  • Unit tests unaffected (./gradlew test)

🤖 Generated with Claude Code

… response

The mutation response from removeCertificate() / removeAnnouncement() no
longer returns fields unrelated to the specific mutation (e.g. announcement
fields are absent after a certificate removal). Refactor all affected
updateXxxAgain / removeCategoryAttributes test methods to call .get() on the
asset by GUID after each mutation so assertions are made against actual
server state rather than the sparse mutation response.

Affects 16 integration test classes across ADLSAssetTest, AirflowAssetTest,
APIAssetTest, AppAssetTest, AnaplanAssetTest, AzureEventHubTest, CubeTest,
DataStudioAssetTest, FileTest, GCSAssetTest, GlossaryTest, InsightsTest,
KafkaTest, PresetAssetTest, S3AssetTest, and SupersetAssetTest.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Chris (He/Him) <cgrote@gmail.com>
Copy link
@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@cmgrote cmgrote added the breaking Breaking change label Mar 12, 2026
@cmgrote cmgrote changed the title chore(deps): consolidate dependency updates fix(tests): adapt integration tests to API change — mutation responses no longer return unrelated fields Mar 12, 2026
@cmgrote cmgrote changed the title fix(tests): adapt integration tests to API change — mutation responses no longer return unrelated fields breaking(tests): mutation responses are now sparse Mar 12, 2026
- cube-assets-builder: default cubeSubFieldCount to 0L for leaf CubeFields
  that have no children in qualifiedNameToChildCount map
- admin-export: guard group-related assertions so they only run when the
  user actually belongs to groups, avoiding false failures for groupless users

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Chris (He/Him) <cgrote@gmail.com>
@cmgrote cmgrote merged commit f798d37 into main Mar 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking Breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0