test: Analyse TBP failure WidgetPropertyNavigation

[NandanAnantharamu]

Summary by CodeRabbit

• Chores
  • Updated the test specification path to focus on "Widget Property Navigation" functionality instead of "Fork Template."

[NandanAnantharamu]

/ci-test-limit-count run_count=100

[github-actions]

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/11793438854.
Cypress dashboard
PR: #37336.

[coderabbitai]

Walkthrough

The changes made in this pull request involve updating the test specification path in the limited-tests.txt file used within a Cypress testing environment. The previous path for the "Fork Template" test has been replaced with a new path that focuses on testing the "Widget Property Navigation" functionality. Other comments in the file remain unchanged.

Changes

File Path	Change Summary
app/client/cypress/limited-tests.txt	Updated test specification path from Fork_Template_spec.js to Widget_property_navigation_spec.ts.

Possibly related PRs

• test: switch branch spec ce #35312: Changes the test specification from Fork_Template_spec.js to SwitchBranches_spec.js.
• test: fix flaky inline editing 2 spec #35426: Updates the test specification from Fork_Template_spec.js to Inline_editing_2_spec.js.
• fix: comment the flaky test to unblock TBP #35540: Modifies the test specification from Fork_Template_spec.js to GraphQL_Binding_Bug16702_Spec.ts.
• fix: Fixed flaky fork template test case #36200: Changes the test specification from Fork_Template_spec.js to Fork_Template_To_App_spec.ts.
• fix: Fixed Bug29566 spec with list widget #36260: Updates the test specification from Fork_Template_spec.js to Bug29566_Spec.ts.
• test: fix DataSourceScheme #36339: Modifies the test specification from Fork_Template_spec.js to DatasourceSchema_spec.ts.
• test: fix canvas context property pane #36356: Changes the test specification from Fork_Template_spec.js to Canvas_Context_Property_Pane_2_spec.js.
• test:Fix canvas context prop01 #36391: Updates the test specification from Fork_Template_spec.js to Canvas_Context_Property_Pane_1_spec.js.
• fix: updating migration repo for DSCrudAndBindings spec #36452: Modifies the test specification from Fork_Template_spec.js to DSCrudAndBindings_Spec.ts.
• chore: create appsmith schema for the pg branch with user and password #36540: Changes the test specification from Fork_Template_spec.js to Command_Click_Navigation_spec.js.
• chore: Updated another set of third party urls #36571: Updates the test specification from Fork_Template_spec.js to Tree_Select_2_spec.ts.
• fix: Fix shareapp case due to load issue #36627: Modifies the test specification from Fork_Template_spec.js to ShareAppTests_Spec.ts.
• test: Enable skipped test related to Autocomplete #36991: Changes the test specification from Fork_Template_spec.js to JS_AC2_spec.ts.
• test: udpated locator for GenetateCrud test #37000: Updates the test specification from Fork_Template_spec.js to Generate_Crud_New_Page_spec.ts.
• test: fix tabs skipped test CE #37023: Modifies the test specification from Fork_Template_spec.js to Tabs_2_spec.ts.

Suggested labels

ok-to-test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

🎉 In the realm of tests, a change we see,
From "Fork Template" to "Widget" it be!
A simple path shift, a focus anew,
In Cypress we trust, for testing is true.
Let's run all the specs, let the code flow,
With each little change, our knowledge will grow! 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d4007e1 and 960ecf1.

📒 Files selected for processing (1)

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

✅ Files skipped from review due to trivial changes (1)

• app/client/cypress/limited-tests.txt

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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