test: flaky analysis for datepicker3

[NandanAnantharamu]

Summary by CodeRabbit

• Tests
  • Updated Cypress test file path from JavaScript to TypeScript
  • Uncommented test path for Anvil Widgets to include in test execution

[coderabbitai]

Walkthrough

The pull request modifies the limited-tests.txt file in the Cypress testing directory. The changes involve replacing a JavaScript test file path with a TypeScript test file path for a Date Picker test and uncommenting a previously commented-out path for Anvil Widgets tests. These modifications adjust the test suite configuration without altering the fundamental test execution process.

Changes

File	Change Summary
app/client/cypress/limited-tests.txt	- Replaced JSEditorIndent_spec.js with DatePicker3_spec.ts - Uncommented Anvil Widgets test path

Suggested labels

ok-to-test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

Possibly related PRs

• test: partial import export areas covered #37661: Modifies limited-tests.txt to include a new test file path
• test: flaky check for onload spec #38429: Updates limited-tests.txt by replacing a JavaScript test with a TypeScript test
• fix: Flaky test case fix #38703: Changes to limited-tests.txt test file specifications

Poem

🧪 In the realm of Cypress tests so bright,
A path uncommented takes its flight
From JS to TS, a subtle dance
Widgets awaken from their trance
Testing magic, line by line! 🔍

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5a98f55 and ed1338b.

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

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: client-unit-tests / client-unit-tests
• GitHub Check: client-lint / client-lint
• GitHub Check: client-build / client-build
• GitHub Check: client-prettier / prettier-check

🔇 Additional comments (2)

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

2-2: LGTM! Path aligns with flaky test analysis objective.

The addition of DatePicker3_spec.ts is consistent with the PR's goal to analyze flaky datepicker tests.

---

5-5: Verify if Anvil Widgets tests should be included.

The uncommented Anvil Widgets path seems unrelated to the datepicker flaky test analysis. Including additional tests might affect the focused analysis of datepicker issues.

Consider keeping only the DatePicker3 test path to maintain a focused test scope for flaky analysis.

---

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

[NandanAnantharamu]

/ci-test-limit-count run_count=50

[github-actions]

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

[github-actions]

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12812720179.
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: 250 Total Passed: 250 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.