Skip to content

[Task] Integration Test — Delete Immunopeptidomics Measurements #1439

Description

@sven1103-agent

Parent Story

#1430

Requirement IDs

MEASUREMENT-R-03

Description

Write and verify the Story-level integration test for immunopeptidomics measurement deletion. The test validates that the implementation Task (#1415) satisfies all acceptance criteria defined in Story #1430. Any failing ACs discovered during this Task are reported as new follow-up Tasks.

The IT belongs in project-management/src/test/groovy/.../measurement/ and runs under the Maven it profile (Spring Boot test slice or @SpringBootTest). It targets the application service layer to avoid mocking internals.

Acceptance Criteria (from parent Story)

  • Given a user with edit rights selects immunopeptidomics measurements for deletion, When they confirm deletion, Then measurements with no attached dataset are deleted successfully.
  • Given a user attempts to delete an immunopeptidomics measurement with an attached dataset, When they confirm deletion, Then the operation fails and the user is informed that the dataset must be removed first.
  • Given a user without edit rights views the measurement page, When they attempt to trigger deletion, Then the deletion action is not available.
  • Given a user deletes an immunopeptidomics measurement successfully, When the operation completes, Then the measurement is also removed from OpenBIS.

Technical Notes

  • Test data: create immunopeptidomics measurements with and without mocked attached datasets.
  • Assertions must cover: successful deletion when no dataset is attached, guard failure when a dataset exists, OpenBIS synchronisation on deletion, and permission-level enforcement.
  • The test must pass with ./mvnw clean verify -Pit before this Task is considered complete.
  • If any AC fails, create new Task(s) referencing this one and the parent Story; do not workaround in this branch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageAn issue that is in discussion to be either scheduled for implepmentation or denied

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions