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: Fix from chatgpt for promise failure #39295

Merged
merged 2 commits into from
Feb 17, 2025
Merged

Conversation

sagar-qa007
Copy link
Contributor

@sagar-qa007 sagar-qa007 commented Feb 14, 2025

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13363538162
Commit: 0701248
Cypress dashboard.
Tags: @tag.AppUrl
Spec:


Mon, 17 Feb 2025 05:49:10 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

Summary by CodeRabbit

  • Tests
    • Streamlined redirection tests by removing an unnecessary sign out step.
    • Enhanced URL validation with improved logging to ensure correct encoding.
    • Refined the testing process to robustly verify that redirection parameters are accurately passed.

@sagar-qa007
Copy link
Contributor Author

/ci-test-limit-count run_count=50 update_snapshot=false specs_to_run=cypress/e2e/Regression/ClientSide/OtherUIFeatures/ApplicationURL_spec.js

Copy link
Contributor

coderabbitai bot commented Feb 14, 2025

Walkthrough

The changes modify the URL redirection tests by removing an unnecessary sign-out step and enhancing the verification process. The test now utilizes a stub for the VisitNAssert method to intercept and verify redirection without real navigation. A logging step that encodes the redirect URL has been added to the assertion, ensuring the correct URL format. Additionally, the exported stub for VisitNAssert in the agHelper object has been updated accordingly.

Changes

File(s) Change Summary
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/ApplicationURL_spec.js Removed the homePage.Signout(true) call in one test case; added a stub call to VisitNAssert and enhanced URL assertion with an encoded redirect URL logging.
app/client/cypress/support/Objects/ObjectsCore.js Introduced/updated the stub for the VisitNAssert method in agHelper to intercept URL redirection calls.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as Test Runner
    participant Test as ApplicationURL_spec.js
    participant Stub as VisitNAssert Stub
    participant Logger as Logger

    Runner->>Test: Start URL redirection test
    Test->>Stub: Call VisitNAssert(redirectUrl)
    Stub-->>Test: Return intercepted call
    Test->>Logger: Log encoded redirectUrl
    Logger-->>Test: Confirm URL format
Loading

Possibly related PRs

Suggested reviewers

  • ApekshaBhosale
  • NandanAnantharamu
  • yatinappsmith

Poem

In the code where tests unfurl,
A redirection tale now twirls,
Signout steps have flown away,
With stubs to guide the test’s display,
Logging dreams in encoded array 🎉
Code blossoms in its playful sway!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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

@github-actions github-actions bot added the Bug Something isn't working label Feb 14, 2025
Copy link

Copy link

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

***** Repeat Run Summary ***** Total Tests with repeat: 200 Total Passed: 200 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 added the ok-to-test Required label for CI label Feb 14, 2025
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

🧹 Nitpick comments (1)
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/ApplicationURL_spec.js (1)

148-159: LGTM! Good use of stubbing for URL redirection testing.

The changes improve test reliability by:

  1. Using stubs to avoid actual navigation
  2. Verifying both the redirection call and URL encoding
  3. Following Cypress best practices

Consider adding these assertions for completeness:

// Verify URL format
cy.wrap(redirectUrl).then((redirectUrl) => {
  expect(redirectUrl).to.match(/^https?:\/\/.+\?embed=true&a=b$/);
});
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7fde87e and 0701248.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/ApplicationURL_spec.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`app/client/cypress/**/**.*`: Review the following e2e test ...

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/OtherUIFeatures/ApplicationURL_spec.js
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: perform-test / rts-build / build
  • GitHub Check: perform-test / client-build / client-build
  • GitHub Check: perform-test / server-build / server-unit-tests
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-lint / client-lint
  • GitHub Check: client-prettier / prettier-check
  • GitHub Check: client-build / client-build

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 merged commit cd519bb into release Feb 17, 2025
45 checks passed
@sagar-qa007 sagar-qa007 deleted the fix/appurlpromisefailure branch February 17, 2025 07:22
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