E2E test of issue #8785: Undefined when reading getUpdated

Import Userrequested to merge
ov/regression_reading_getUpdated into develop

Adding a test to reproduce the issue fixed in GH-8785

Motivation and context

The issue dealt with inconsistent state of the user's job cache after he deletes a frame, tries to save the job, suddenly gets an unexpected network error from the server, then tries to save the job again.

How has this been tested?

Arranged state (before() hook)
  • Check deleted frame visibility box form the user's pop down menu (to confirm deletion later)
  • Open a job from a task
  • Pick a frame in the UI
Test case
  • Delete the chosen frame
  • Confirm that the deletion did happen (assert that a .restore element is visible)
  • Try to save - but instead of 200 receive a stubbed response with 502
  • Try to save again - this time yielding 200 OK without no unexpected errors

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • New Features

    • Introduced a new end-to-end test for job metadata consistency after frame deletion.

  • Bug Fixes

    • Validated behavior when saving a job after frame deletion, ensuring proper error handling and recovery.

Merge request reports