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

test: Skipping test becasuea of an open Issue[RestAPIDatasrouce spec] #37354

Open
wants to merge 2 commits into
base: release
Choose a base branch
from

Conversation

NandanAnantharamu
Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu commented Nov 13, 2024

We observe an intermittent issue while create RestAPI DS. I have updated the test to handle this usecase.
raised below bug
(#37353)

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling in the end-to-end test for creating a REST datasource.
    • Enhanced robustness of UI interactions to prevent timing issues during test execution.
  • Tests

    • Updated assertions and added checks for specific values to ensure correct URL input before saving the datasource.
    • Clarified comments for better understanding of test logic and previous issues.
    • Temporarily disabled the test suite due to an associated issue (Bug 14566).

Warning

Tests have not run on the HEAD a38a66c yet


Wed, 13 Nov 2024 10:39:02 UTC

Copy link
Contributor

coderabbitai bot commented Nov 13, 2024

Walkthrough

The pull request modifies the Cypress end-to-end test for creating a REST datasource. Key changes include marking the test suite as skipped due to an associated issue, enhancing the method for clicking the "store as datasource" button to ensure element visibility, and adding a check for a specific URL in the document body. Comments have been clarified, and the assertion for the datasource presence remains intact, while previous failure comments have been removed.

Changes

File Change Summary
app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js Marked test suite as skipped; improved element visibility check for clicking button; added URL existence check and clarified comments.

Possibly related PRs

Suggested labels

ok-to-test

Suggested reviewers

  • ApekshaBhosale
  • sagar-qa007

🎉 In the realm of tests, where bugs may roam,
Enhancements were made to bring them home.
A click with assurance, a URL to find,
With clearer comments, our tests are refined!
So here's to the changes, robust and bright,
In the world of Cypress, we now take flight! 🚀


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6217fc9 and a38a66c.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js

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 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.

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.

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit-count run_count=100

@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test labels Nov 13, 2024
Copy link

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: 3

🧹 Outside diff range and nitpick comments (1)
app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js (1)

15-35: Consider restructuring the test for better reliability

  1. Combine related assertions for better test flow
  2. Consider breaking this into smaller, focused test cases
  3. Add error handling for API responses

Example structure:

it("should create REST datasource with valid URL", function () {
  apiPage.CreateAndFillApi(testdata.baseUrl + testdata.methods);
  
  // Save as datasource
  cy.get(apiPage._saveAsDS)
    .should('be.visible')
    .and('be.enabled')
    .click()
    .then(() => {
      // Verify no error toasts
      agHelper.AssertElementAbsence(locators._specificToast("Duplicate key error"));
    });

  // Configure datasource
  cy.get(apiPage._urlInputField)
    .should('exist')
    .and('be.visible')
    .type(testdata.restApiUrl);

  // Save and verify
  cy.saveDatasource();
  cy.get(apiPage._datasourceURLHighlight)
    .should('be.visible')
    .and('contain', testdata.restApiUrl);
});
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8773bdd and 6217fc9.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
🔇 Additional comments (1)
app/client/cypress/e2e/Sanity/Datasources/RestApiDatasource_spec.js (1)

18-21: LGTM! Good error handling

The negative assertion for the error toast is well implemented.

Comment on lines 23 to 31
cy.get("body").then((body) => {
if (
body.find('[value="http://host.docker.internal:5001"]').length < 1
) {
cy.get('[placeholder="https://example.com"]').type(
"http://host.docker.internal:5001",
);
}
});
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

Multiple violations of Cypress best practices

  1. Avoid using attribute selectors
  2. Move hardcoded URLs to test data
  3. Use data-cy attributes for element selection
-cy.get("body").then((body) => {
-  if (body.find('[value="http://host.docker.internal:5001"]').length < 1) {
-    cy.get('[placeholder="https://example.com"]').type(
-      "http://host.docker.internal:5001",
-    );
-  }
-});
+const TEST_URL = testdata.restApiUrl;
+cy.get(apiPage._urlInputField)
+  .should('exist')
+  .then(($el) => {
+    if ($el.val() !== TEST_URL) {
+      cy.get(apiPage._urlInputField).type(TEST_URL);
+    }
+  });

Also, update the testdata.json to include:

{
  "restApiUrl": "http://host.docker.internal:5001"
}

cy.saveDatasource();
cy.contains(".datasource-highlight", "http://host.docker.internal:5001"); //failing here since Save as Datasource is broken
cy.contains(".datasource-highlight", "http://host.docker.internal:5001");
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

Use data attributes and avoid hardcoded values

Replace class selector with data attribute and use the URL from test data.

-cy.contains(".datasource-highlight", "http://host.docker.internal:5001");
+cy.get(apiPage._datasourceURLHighlight)
+  .should('contain', testdata.restApiUrl);

Committable suggestion skipped: line range outside the PR's diff.

Comment on lines +16 to +17
agHelper.WaitUntilEleAppear(apiPage._saveAsDS);
cy.get(apiPage._saveAsDS).click({ force: true });
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

Avoid using force: true in click operations

Replace the force click with proper element state verification:

 agHelper.WaitUntilEleAppear(apiPage._saveAsDS);
-cy.get(apiPage._saveAsDS).click({ force: true });
+cy.get(apiPage._saveAsDS)
+  .should('be.visible')
+  .and('be.enabled')
+  .click();
📝 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
agHelper.WaitUntilEleAppear(apiPage._saveAsDS);
cy.get(apiPage._saveAsDS).click({ force: true });
agHelper.WaitUntilEleAppear(apiPage._saveAsDS);
cy.get(apiPage._saveAsDS)
.should('be.visible')
.and('be.enabled')
.click();

Copy link

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11809607457.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:
To know the list of identified flaky tests - Refer here

***** Repeat Run Summary ***** Total Tests with repeat: 0 Total Passed: 0 Total Failed: 0 Total Skipped: 0 *****************************

@NandanAnantharamu NandanAnantharamu changed the title test: updated the spec to check if the API is visible or not test: Skipping test becasuea of an open Issue[RestAPIDatasrouce spec] Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant