Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E test of issue #8785: Undefined when reading getUpdated #8843

Open
wants to merge 17 commits into
base: develop
Choose a base branch
from

Conversation

archibald1418
Copy link
Contributor

@archibald1418 archibald1418 commented Dec 18, 2024

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.

Copy link
Contributor

coderabbitai bot commented Dec 18, 2024

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request introduces a new Cypress end-to-end test file targeting issue #8785, which focuses on handling job metadata inconsistencies after frame deletion. The test simulates a scenario where a job might crash during saving after removing a frame. It includes functions to delete a frame, save a job, and implements a middleware to intercept and manage PATCH request responses, ensuring robust error handling and recovery mechanisms.

Changes

File Change Summary
tests/cypress/e2e/issues_prs2/issue_8785_Cannot_read_properties_of_undefined_reading_getUpdated.js Added new Cypress test for handling job metadata after frame deletion, with middleware to simulate network errors and test recovery scenarios

Poem

🐰 A Rabbit's Tale of Frames and Saves

In Cypress realm, where tests explore,
A frame deleted, a job to restore
Network errors dance, then softly fade
With resilience, our test is made!
🔧 Debugging magic, code's brave knight 🛡️


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (5)
tests/cypress/e2e/issues_prs2/issue_8785_Cannot_read_properties_of_undefined_reading_getUpdated.js (5)

7-7: Consider using more specific imports

Instead of importing the entire const file, consider destructuring only the required taskName constant for better code maintainability and clarity.

-import { taskName } from '../../support/const';
+import type { taskName } from '../../support/const';

9-15: Improve test setup documentation and constants

Consider the following improvements:

  1. Document why frame 4 is specifically chosen for the test
  2. Extract the frame number into a named constant
+const TEST_FRAME_NUMBER = 4; // Document why this frame is chosen
 context('When saving after deleting a frame, job metadata is inconsistent.', () => {
     const issueId = '8785';

     before(() => {
         cy.openTaskJob(taskName);
-        cy.goToNextFrame(4);
+        cy.goToNextFrame(TEST_FRAME_NUMBER);
     });

35-36: Remove debug console.log statements

Debug logging statements should be removed from the test code.

     if (calls === 0) {
-        console.log(calls);
         calls++;
         res.send(badResponseStub);
     } else {
-        console.log(calls);
         req.continue({ statusCode: 200, body: 'OK' });
     }

Also applies to: 39-40


52-69: Address TODO and FIXME comments

There are several unresolved comments that need attention:

  1. TODO: refactor saveJob with necessary status
  2. FIXME: assertions and response stubbing comments

Please either implement the suggested changes or create issues to track these improvements.

Would you like me to help create GitHub issues to track these improvements?


70-74: Consider consolidating save job tests

The consecutive save job tests with different status codes could be combined into a more descriptive test case using cy.then() for better flow control.

-// Send bad PATCH
-cy.saveJob('PATCH', 502);
-
-// Send again
-cy.saveJob('PATCH', 200);
+cy.then(() => {
+    // First attempt should fail
+    cy.saveJob('PATCH', 502).then(() => {
+        // Second attempt should succeed
+        cy.saveJob('PATCH', 200);
+    });
+});
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba475a9 and f45e810.

📒 Files selected for processing (1)
  • tests/cypress/e2e/issues_prs2/issue_8785_Cannot_read_properties_of_undefined_reading_getUpdated.js (1 hunks)


// TODO: refactor saveJob with necessary status

// Check that frame is deleted
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add missing frame deletion assertions

The comment indicates a need for frame deletion verification, but no assertions are implemented. Consider adding appropriate checks.

// Add these assertions after line 54
cy.get('.cvat-player-frame-selector').should('have.value', TEST_FRAME_NUMBER - 1);
cy.get('.cvat-player-restore-frame').should('exist');

Comment on lines 30 to 44
function middleware() {
let calls = 0;
const badResponseStub = { statusCode: 502, body: 'Network error' };
function handle(req, res) {
if (calls === 0) {
console.log(calls);
calls++;
res.send(badResponseStub);
} else {
console.log(calls);
req.continue({ statusCode: 200, body: 'OK' });
}
}
return handle;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Improve middleware implementation

The middleware implementation could benefit from several improvements:

  1. Add error handling for edge cases
  2. Use typed response objects
  3. Add logging for debugging purposes
 function middleware() {
     let calls = 0;
-    const badResponseStub = { statusCode: 502, body: 'Network error' };
+    const badResponseStub = {
+        statusCode: 502,
+        body: { error: 'Network error' },
+        headers: { 'content-type': 'application/json' },
+    };
     function handle(req, res) {
+        try {
             if (calls === 0) {
                 calls++;
                 res.send(badResponseStub);
             } else {
                 req.continue({ statusCode: 200, body: 'OK' });
             }
+        } catch (error) {
+            cy.log(`Middleware error: ${error.message}`);
+            throw error;
+        }
     }
     return handle;
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
function middleware() {
let calls = 0;
const badResponseStub = { statusCode: 502, body: 'Network error' };
function handle(req, res) {
if (calls === 0) {
console.log(calls);
calls++;
res.send(badResponseStub);
} else {
console.log(calls);
req.continue({ statusCode: 200, body: 'OK' });
}
}
return handle;
}
function middleware() {
let calls = 0;
const badResponseStub = {
statusCode: 502,
body: { error: 'Network error' },
headers: { 'content-type': 'application/json' },
};
function handle(req, res) {
try {
if (calls === 0) {
calls++;
res.send(badResponseStub);
} else {
req.continue({ statusCode: 200, body: 'OK' });
}
} catch (error) {
cy.log(`Middleware error: ${error.message}`);
throw error;
}
}
return handle;
}

Copy link

Please retry analysis of this Pull-Request directly on SonarQube Cloud

@archibald1418 archibald1418 changed the title [WIP] Regression e2e-test of issue #8785 Regression e2e-test of issue #8785 Dec 20, 2024
@archibald1418 archibald1418 changed the title Regression e2e-test of issue #8785 E2E test of issue #8785: Undefined when reading getUpdated Dec 20, 2024
@codecov-commenter
Copy link

codecov-commenter commented Dec 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.92%. Comparing base (12f886c) to head (5d67f16).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8843      +/-   ##
===========================================
+ Coverage    73.88%   73.92%   +0.03%     
===========================================
  Files          408      408              
  Lines        44104    44104              
  Branches      3986     3986              
===========================================
+ Hits         32586    32603      +17     
+ Misses       11518    11501      -17     
Components Coverage Δ
cvat-ui 78.43% <ø> (+0.08%) ⬆️
cvat-server 70.08% <ø> (ø)


cy.intercept(routeMatcher, badResponse).as('patchError');

clickDelete();
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
clickDelete();
clickDeleteFrame();

.gitignore Outdated
@@ -49,8 +49,9 @@ yarn-error.log*

# Ignore all the installed packages
node_modules
venv/
venv*/
Copy link
Contributor

Choose a reason for hiding this comment

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

I noticed a slight inconsistency here. We have /.*env* on line 7 in this file. Let’s move line 7 here so that all the ignored package rules are grouped together in one place.

.gitignore Outdated
.venv/
.env/
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldnt /.*env* already cover this case?

Copy link
Contributor

Choose a reason for hiding this comment

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

Lets name this issue_8785_update_job_metadata


import { taskName } from '../../support/const';

context('When saving after deleting a frame, job metadata is inconsistent.', () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
context('When saving after deleting a frame, job metadata is inconsistent.', () => {
context('The UI remains stable even when the metadata request fails.', () => {

Comment on lines 12 to 18
function checkDeletedFrameVisibility() {
cy.openSettings();
cy.get('.cvat-workspace-settings-show-deleted').within(() => {
cy.get('[type="checkbox"]').should('not.be.checked').check();
});
cy.closeSettings();
}
Copy link
Contributor

Choose a reason for hiding this comment

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

The code of this funcion is duplicated from case_delete_frame. Lets create a support command that will change this settings and use it here and in case_delete_frame.

cy.on('uncaught:exception', (err) => {
expect(err.code).to.equal(badResponse.statusCode);
return false;
}); // On 502, Cypres always triggers a Node exception
Copy link
Contributor

Choose a reason for hiding this comment

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

We dont really need this comment

const badResponse = { statusCode: 502, body: 'A horrible network error' };

cy.on('uncaught:exception', (err) => {
expect(err.code).to.equal(badResponse.statusCode);
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to additionally check that error message is badResponse.body?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants