chore: Reverted the change

[sagar-qa007]

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=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

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

• Yes
• No

Summary by CodeRabbit

• Chores
  • Updated test file path to transition focus from Iframe component testing to Fork Template component testing in the Cypress testing environment.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the limited-tests.txt file in the Cypress testing environment. It changes the specified test file path from testing the Iframe component to focusing on the Fork Template component. The overall structure of the file remains unchanged, including comments about running all specs and the purpose of the ci-test-limit command.

Changes

File Path	Change Summary
app/client/cypress/limited-tests.txt	Updated test file path from cypress/e2e/Regression/ClientSide/Widgets/Iframe/IframeTest_spec.ts to cypress/e2e/Regression/ClientSide/Templates/Fork_Template_spec.js

Possibly related PRs

• fix: Fixed flaky fork template test case #36200: Updates the limited-tests.txt file, changing the test specification from Fork_Template_spec.js to Fork_Template_To_App_spec.ts.
• fix: Fix shareapp case due to load issue #36627: Changes the limited-tests.txt file to update the test specification from Fork_Template_spec.js to ShareAppTests_Spec.ts.
• test: Enable skipped test related to Autocomplete #36991: Updates the limited-tests.txt file by replacing the test specification path from Fork_Template_spec.js to JS_AC2_spec.ts.
• chore: Reverted appsmith url #37267: Modifies the limited-tests.txt file to change the test specification from Fork_Template_spec.js to a different test file.
• fix: Fix for the test case #37936: Updates the limited-tests.txt file, replacing the test specification from Fork_Template_spec.js to DS_Bug26941_Spec.ts.
• fix: Fix flaky test case for the iframe spec #38018: Changes the limited-tests.txt file to replace the test specification from Fork_Template_spec.js to IframeTest_spec.ts.

Suggested labels

ok-to-test

Suggested reviewers

• yatinappsmith
• ApekshaBhosale

🎉 In the land of code where tests do roam,
A path was changed to find a new home.
From Iframe's grasp to Templates' embrace,
The tests now dance in a different space.
With Cypress ready, let the specs take flight,
In the world of testing, all feels just right! 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6f42527 and 6246096.

📒 Files selected for processing (1)

• app/client/cypress/limited-tests.txt (1 hunks)

---

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