Class DatasetsFactorHintCommitRestTest

java.lang.Object
org.glassfish.jersey.test.JerseyTest
All Implemented Interfaces:
org.springframework.beans.factory.Aware, org.springframework.context.ApplicationContextAware

@Tag("integration") public class DatasetsFactorHintCommitRestTest extends BaseJerseyIntegrationTest5
A design-commit factor item carrying ONLY gemmaId plus one relevance hint leaves everything else about the factor as it was: name, category, factor values and sample assignments.

cab writes subsetRelevance / baselineRelevance on an EXISTING factor this way (CAB_TO_GEMBRO_2026_09_12_YES_PIN_THE_FACTOR_ITEM_SURVIVORS_IN_THE_DEFAULT_SUITE). The code carries omitted fields forward — the service applies factor metadata only when non-null, and REST keeps every factor value a section does not mention (declared-delete) — but the nearest existing test, DatasetsCurationCommitRestTest#testSubsetRelevanceRoundTripsAndAnOverrideOnlyCommitIsNotANoOp, asserts none of the survivors and is @Tag("slow"), so it is not in the default suite.

Runs end to end against gemdtest — REST mapping, service apply, persistence — because the survivors are a property of that whole path, not of any one layer a mock could stand in for.

Out of scope here: supportingEvidence. A factor that HAS evidence answers 400 to an item that omits it (requireEvidenceEchoed); the seeded factor carries none, so no echo is needed.

  • Constructor Details

    • DatasetsFactorHintCommitRestTest

      public DatasetsFactorHintCommitRestTest()
  • Method Details

    • seedExperiment

      @BeforeEach public void seedExperiment()
    • removeExperiment

      @AfterEach public void removeExperiment()
    • aSubsetRelevanceOnlyItemLeavesNameCategoryValuesAndAssignmentsIntact

      @Test public void aSubsetRelevanceOnlyItemLeavesNameCategoryValuesAndAssignmentsIntact()
    • aBaselineRelevanceOnlyItemLeavesNameCategoryValuesAndAssignmentsIntact

      @Test public void aBaselineRelevanceOnlyItemLeavesNameCategoryValuesAndAssignmentsIntact()