Test to confirm correct UI and cache state after frame deletion

[archibald1418]

Motivation and context

Fix #8872 dealt with incorrect states of UI and cache after frame deletion. The frame was not being deleted and the cache was not updated properly to reflect the changes.

How has this been tested?

Set up

• open Main task job
• save default cvat.config.jobMetaDataReloadPeriod value from cvat-core/src/config.ts
• temporarily set jobMetaDataReloadPeriod to a small value (100 ms) for the sake of easier testing

Test suite

• Inside the job, wait for the small job metadata reload period to elapse
• Transition to the next frame by clicking the next button on the player
• Verify that GET /data/meta is sent and that the response has frames in it.
• Save current frame number to the variable frameNum
• Delete the frame: click on the bin, click on 'Delete' button in the modal
• Ensure that 'Restore frame' button is absent
• Make sure that the frame is deleted by asserting that current frame has number frameNum + 1 (the next frame in the dataset)
• Click Save to send PATCH to /data/meta.
• Intercept the request to validate that response has deleted_frames property, that it's an Array and that it contains the deleted frame number frameNum
• Assert that deleted_frames array contains one element: frameNum

Tear down

• Set jobMetaDataReloadPeriod back to the saved default value

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.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.90%. Comparing base (c6ec4eb) to head (dbae90e).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8949      +/-   ##
===========================================
+ Coverage    73.83%   73.90%   +0.06%     
===========================================
  Files          417      417              
  Lines        44602    44598       -4     
  Branches      4031     4031              
===========================================
+ Hits         32934    32958      +24     
+ Misses       11668    11640      -28     

Components	Coverage Δ
cvat-ui	78.39% <ø> (+0.11%)	⬆️
cvat-server	70.08% <67.97%> (+0.01%)	⬆️

[klakhov]

It seems we wont be using year in headers anymore.

LGTM

[bsekachev]

I will suggest being more specific here in naming if we add global Cypress command.
We probably have many Save buttons across the application.

So, maybe clickSaveAnnotationView.
Additionally I will ask to search by contains('Save').click over the tests and replace findings

I found at least two more places with this code (case 92, case 91):

cy.get('button').contains('Save').click();
cy.get('button').contains('Save').trigger('mouseout');

[bsekachev]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud