test: to check flaky behaviour MaintainContext spec

[NandanAnantharamu]

Summary by CodeRabbit

• New Features

  • Updated the testing focus to prioritize the "Maintain Context & Focus" feature within the IDE.

• Bug Fixes

  • Enhanced testing coverage for the IDE functionality to ensure better performance and reliability.

[coderabbitai]

Walkthrough

The pull request introduces a modification in the Cypress testing framework's configuration, specifically changing the path for limited tests. The focus shifts from testing the "Fork Template" functionality to the "Maintain Context & Focus" feature within the IDE. This change reflects a strategic decision to prioritize testing for a different aspect of the application while retaining the option to run all tests.

Changes

File Path	Change Summary
app/client/cypress/limited-tests.txt	Changed test path from Fork_Template_spec.js to MaintainContext&Focus_spec.js for limited tests.

Possibly related issues

• [Bug]: flaky spec MaintainContext&Focus #36362: The change in test focus to MaintainContext&Focus_spec.js aligns with addressing the flaky test issue reported in this open bug.

Possibly related PRs

• fix: Fixed flaky fork template test case #36200: This PR also modifies the limited-tests.txt file to change the test specification, indicating a similar shift in testing priorities.
• chore: fix select1 spec #36228: Updates the limited-tests.txt file by commenting out the Fork_Template_spec.js entry and adding a new entry, reflecting a change in testing focus.
• fix: Fixed Bug29566 spec with list widget #36260: Replaces the Fork_Template_spec.js entry with another test, aligning with the main PR's theme of altering test specifications.

Suggested labels

Task, ok-to-test

🌟 In the realm of tests, a shift we see,
From "Fork Template" to "Focus" with glee.
Cypress now dances, a new path to tread,
For "Maintain Context" is where we are led.
With each little change, our code does refine,
Testing the features, making them shine! ✨

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 27aeb4d and e8eb450.

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

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

2-2: Excellent work on updating the limited test specification path! 👍

The change in focus from testing "Fork Template" to "Maintain Context & Focus" in the IDE context is a strategic move. It's important to prioritize testing for the most critical aspects of the application.

As you write the new test specification, remember to follow the best practices outlined in the additional instructions:

• Avoid using cy.wait, cy.pause, and agHelper.sleep().
• Use locator variables and data-* attributes for selectors.
• Avoid XPaths, attributes, and complex CSS paths.
• Perform logins, logouts, and signups via API.
• Use multiple assertions for expect statements and avoid using strings.
• Avoid using it.only, after, and afterEach in test cases.

By adhering to these guidelines, you'll ensure that the Cypress test code is maintainable, reliable, and efficient. Keep up the great work! 🌟

---

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 generate interesting stats about this repository and render them as a table.
  -- @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

[github-actions]

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

[github-actions]

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

[github-actions]

This PR has been closed because of inactivity.