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: fix Embedd Spec #37263

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

test: fix Embedd Spec #37263

wants to merge 3 commits into from

Conversation

NandanAnantharamu
Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu commented Nov 6, 2024

updated the button click logic in the test

Warning

Tests have not run on the HEAD a8eb509 yet


Fri, 08 Nov 2024 07:26:06 UTC

Summary by CodeRabbit

  • Bug Fixes

    • Improved the reliability of the embed settings tests by replacing direct Cypress commands with helper functions.
    • Commented out flaky tests to enhance stability.
  • New Features

    • Shifted focus of testing from "Fork Template" to "Embed Settings," ensuring comprehensive validation of the embed functionality.
  • Documentation

    • Updated test specification paths to reflect the new focus on embed settings.

Copy link
Contributor

coderabbitai bot commented Nov 6, 2024

Walkthrough

The changes in this pull request involve updates to the Cypress end-to-end test suite for embed settings. Key modifications include replacing direct Cypress commands with helper functions for element interactions and updating the test specification path in the limited-tests.txt file to focus on embed settings. The overall structure and logic of the tests remain unchanged, with adjustments made to improve the reliability and maintainability of the test suite.

Changes

File Path Change Summary
app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js Replaced direct Cypress commands with helper functions for clicking elements; added wait for confirmation message.
app/client/cypress/limited-tests.txt Updated test specification path from Fork Template to Embed Settings.

Possibly related PRs

Suggested labels

ok-to-test, Tech Debt

Suggested reviewers

  • ApekshaBhosale
  • sagar-qa007

🎉 In the world of tests, we've made a change,
Helper functions now lead, it's time to rearrange!
From Fork Template to Embed Settings we glide,
With each click and assertion, we take it in stride.
Reliability's the goal, and we've set the pace,
Cheers to cleaner tests in this testing race! 🥳


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between da3f7e7 and a8eb509.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_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.

@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 6, 2024
Copy link

github-actions bot commented Nov 6, 2024

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit-count run_count=25

Copy link

github-actions bot commented Nov 6, 2024

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

🧹 Outside diff range and nitpick comments (3)
app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js (3)

Line range hint 77-78: Remove explicit sleep commands

Replace _.agHelper.Sleep() with proper Cypress wait conditions using cy.waitUntil() or appropriate assertions.

- _.agHelper.Sleep(2000);
+ cy.waitUntil(() => {
+   return cy.window().then((win) => {
+     return win.document.readyState === 'complete';
+   });
+ });

Also applies to: 144-145


Line range hint 82-142: Refactor test structure

The test combines multiple scenarios in a single test case. Consider splitting into separate test cases:

  1. "should limit embedding"
  2. "should allow embedding everywhere"
  3. "should disable embedding everywhere"

This improves test isolation and maintenance.


Line range hint 6-20: Improve iframe handling reliability

Replace the current iframe handling with a more robust approach:

const getIframeBody = () => {
  return cy
    .get(".t--widget-iframewidget iframe")
    .should('be.visible')
+   .should('have.prop', 'complete', true)
    .its("0.contentDocument.body")
    .should("not.be.empty")
    .then(cy.wrap);
};
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ec246fd and da3f7e7.

📒 Files selected for processing (2)
  • app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js (2 hunks)
  • app/client/cypress/limited-tests.txt (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_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.
app/client/cypress/limited-tests.txt (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 (2)
app/client/cypress/limited-tests.txt (1)

2-2: LGTM! Verifying the test file path.

The updated test specification path aligns with the PR objectives to focus on embed settings tests.

Let's verify the existence of the specified test file:

✅ Verification successful

Test file path verified successfully

The specified test file exists at the correct location in the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the new test file exists
# Expected: The file should exist in the specified path

fd "EmbedSettings_spec.js" app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/

Length of output: 167

app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js (1)

41-41: LGTM: Improved element interaction

Good change to use the helper function for clicking elements. This makes the code more maintainable and consistent.

Also applies to: 67-67

Copy link

github-actions bot commented Nov 6, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11705702957.
Cypress dashboard url: Click here!
All Cypress tests have passed 🎉🎉🎉

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

Copy link

github-actions bot commented Nov 6, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11705676417.
Cypress dashboard url: Click here!
All Cypress tests have passed 🎉🎉🎉

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

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit

Copy link

github-actions bot commented Nov 8, 2024

Copy link

github-actions bot commented Nov 8, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11737896921.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit-count run_count=25

Copy link

github-actions bot commented Nov 8, 2024

Copy link

github-actions bot commented Nov 8, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11738256344.
Cypress dashboard url: Click here!
All Cypress tests have passed 🎉🎉🎉

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

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