test: analyse TBP failure Datepicker2

[NandanAnantharamu]

Summary by CodeRabbit

• Bug Fixes

  • Updated the test file reference for limited tests to ensure accurate execution of the DatePicker2 tests.

• Documentation

  • Maintained comments regarding test execution commands for clarity.

[coderabbitai]

Walkthrough

The changes in this pull request involve updating a text file that specifies which Cypress test cases to run. The reference to the test file Fork_Template_spec.js has been changed to DatePicker2_spec.js in app/client/cypress/limited-tests.txt. Other comments in the file remain unchanged, including those about running all specs and the ci-test-limit command.

Changes

File Path	Change Summary
app/client/cypress/limited-tests.txt	Updated test file reference from Fork_Template_spec.js to DatePicker2_spec.js.

Possibly related PRs

• test: fix datepicker tests #37042: This PR modifies the DatePicker2_spec.js test file, which is directly referenced in the main PR's changes to the limited-tests.txt file, indicating a shift in focus to the DatePicker tests.
• test: fixed datepicker skipped tests set 2 #37126: This PR also addresses the DatePicker tests, specifically activating previously skipped tests and updating methods related to date selection, aligning with the changes made in the main PR regarding the DatePicker test file.

Suggested labels

skip-changelog, ok-to-test, Test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

Poem

In the land of tests, a change was made,
From Fork to DatePicker, a new path laid.
With Cypress in hand, we run with glee,
Testing the widgets, as happy as can be!
So here’s to the code, and all that we do,
Each line a step, in our testing brew! 🎉

---

📜 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 b44b55a.

📒 Files selected for processing (1)

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

🧰 Additional context used

📓 Path-based instructions (1)

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 (1)

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

2-2: Verify the test file exists and is the correct target

The path change aligns with the PR objective to analyze TBP failure in Datepicker2. Let's verify the file exists and is the intended target.

---

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.

[NandanAnantharamu]

/ci-test-limit-count run_count=100

[github-actions]

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

[github-actions]

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

[github-actions]

This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected.