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

fix: Updated fix for embedSettings spec #38195

Merged
merged 2 commits into from
Dec 17, 2024
Merged

Conversation

sagar-qa007
Copy link
Contributor

@sagar-qa007 sagar-qa007 commented Dec 17, 2024

Description

Updated new code for the coping url from the clipboard in cypress as older code has been deprecated.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.Settings"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12368303561
Commit: 049ddf4
Cypress dashboard.
Tags: @tag.Settings
Spec:


Tue, 17 Dec 2024 07:49:08 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Bug Fixes

    • Improved reliability of clipboard interactions in end-to-end tests for embed settings.
  • New Features

    • Updated test specifications to include a new entry for "EmbedSettings" in the testing suite, replacing the previous "Fork_Template" entry.

Copy link
Contributor

coderabbitai bot commented Dec 17, 2024

Walkthrough

The pull request introduces modifications to the Cypress end-to-end test for embed settings, primarily focusing on improving clipboard functionality testing. The changes involve replacing the clipboard text reading method with a stub that mocks the writeText method. The test structure remains consistent, maintaining the core functionality of testing embed settings, including scenarios for limiting, allowing, and disabling embedding.

Changes

File Change Summary
app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js Updated clipboard interaction method, replacing cy.window().its("navigator.clipboard").invoke("readText") with a stub mocking clipboard's writeText method
app/client/cypress/limited-tests.txt Replaced "Fork_Template_spec.js" test specification with "EmbedSettings_spec.js"

Sequence Diagram

sequenceDiagram
    participant Test as Cypress Test
    participant App as Application
    participant Clipboard as Clipboard Stub

    Test->>App: Navigate to Embed Settings
    Test->>App: Modify Embed Settings
    Test->>Clipboard: Mock writeText Method
    Test->>App: Verify Iframe Submission
Loading

Possibly related PRs

Suggested labels

Bug, ok-to-test, Test, skip-changelog

Suggested reviewers

  • ApekshaBhosale
  • NandanAnantharamu

Poem

🖥️ In the realm of tests, a clipboard's dance,
Mocking stubs with a playful glance,
Embed settings twirl, iframes take flight,
Cypress weaves magic, testing just right!
A digital ballet of code's delight 🧪

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


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.

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.

@sagar-qa007 sagar-qa007 changed the title Fix: Updated fix Fix: Updated fix for embedSettings spec Dec 17, 2024
@sagar-qa007
Copy link
Contributor Author

/ci-test-limit-count run_count=50

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

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

Line range hint 19-24: Remove cy.wait and agHelper.Sleep calls

The use of explicit waits and sleep calls violates the coding guidelines. Replace them with proper Cypress wait strategies.

Consider using these alternatives:

- _.agHelper.Sleep(5000)
+ cy.get('.t--widget-iframewidget iframe').should('be.visible')

- cy.wait(8000)
+ cy.get('.t--widget-iframewidget iframe').should('have.attr', 'src').and('not.be.empty')

- _.agHelper.Sleep(2000)
+ cy.get('.t--admin-settings-APPSMITH_ALLOWED_FRAME_ANCESTORS').should('be.visible')

Also applies to: 54-55, 82-82, 102-102, 122-122


Line range hint 28-32: Avoid hardcoded URLs in tests

Using hardcoded URLs makes tests brittle and environment-dependent.

Consider:

  1. Using environment variables
  2. Generating test data dynamically
  3. Using mock data
- "https://app.appsmith.com/applications/6752ba5904a5f464099437ec/pages/6752ba5904a5f464099437f3"
+ Cypress.env('TEST_IFRAME_URL')

Line range hint 63-142: Refactor test structure

The current implementation combines multiple test cases into a single "it" block. This makes it harder to debug failures and understand test results.

Consider splitting into separate test cases:

it("1. Should limit embedding", function () {
  // Test limiting embedding
});

it("2. Should allow embedding everywhere", function () {
  // Test allowing embedding
});

it("3. Should disable embedding everywhere", function () {
  // Test disabling embedding
});
🧹 Nitpick comments (1)
app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js (1)

Line range hint 4-4: Add more specific test tags

The current tag @tag.Settings is too generic. Consider adding more specific tags for better test organization.

Example:

- { tags: ["@tag.Settings"] }
+ { tags: ["@tag.Settings", "@tag.EmbedSettings", "@tag.Regression"] }
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3e9967 and 1afae42.

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

2-2: LGTM!

The test specification update aligns with the PR objective.

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

51-53: LGTM: Clipboard stub implementation

The clipboard stub implementation is correct and follows Cypress best practices.

Copy link

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12365551194.
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: 50 Total Passed: 50 Total Failed: 0 Total Skipped: 0 *****************************

Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu left a comment

Choose a reason for hiding this comment

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

Lgtm

@sagar-qa007 sagar-qa007 changed the title Fix: Updated fix for embedSettings spec fix: Updated fix for embedSettings spec Dec 17, 2024
@sagar-qa007 sagar-qa007 added the ok-to-test Required label for CI label Dec 17, 2024
@github-actions github-actions bot added the Bug Something isn't working label Dec 17, 2024
@sagar-qa007 sagar-qa007 merged commit d905a4c into release Dec 17, 2024
51 checks passed
@sagar-qa007 sagar-qa007 deleted the fix/embeededcopyisuue branch December 17, 2024 07:51
@coderabbitai coderabbitai bot mentioned this pull request Dec 26, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working ok-to-test Required label for CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants