test: analyse postgress2 failure

[NandanAnantharamu]

Summary by CodeRabbit

• Tests
  • Updated the automated test configuration to focus on a revised regression scenario, ensuring improved quality assurance.

[coderabbitai]

Walkthrough

The pull request updates the test specification in the limited-tests.txt file by replacing the entry for BooleanEnum_Spec.ts with Postgres2_Spec.ts. The change shifts the focus from one test file to another within the same testing structure. The update preserves the overall file context while modifying the specific test case to be executed in the regression suite.

Changes

File	Change Summary
app/client/cypress/limited-tests.txt	Replaced BooleanEnum_Spec.ts with Postgres2_Spec.ts to update the test specification.

Possibly related PRs

• fix: Fix for the test case #37936: Modifies limited-tests.txt by altering test specifications, closely related to this update.
• fix:Widget Column test case fix #38045: Changes the test file entry in limited-tests.txt, aligning with the modifications made here.
• test: Skipping one test in API Edit Spec for functional bugs #38115: Also refines test specifications in limited-tests.txt, presenting a similar code-level change.

Suggested labels

skip-changelog, ok-to-test, Test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007
• yatinappsmith

Poem

In the realm of tests so fine,
A change emerges line by line,
From Boolean’s tale to Postgres’ might,
Our scripts shall now ignite!
Cheers to code that flows just right 🚀
Happy testing in every byte!

---

📜 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 37b4aca and 5a85476.

📒 Files selected for processing (1)

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

🧰 Additional context used

📓 Path-based instructions (1)

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

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.

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

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

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

🔇 Additional comments (1)

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

2-2: Spec Update Verification:
The test specification now points to cypress/e2e/Regression/ServerSide/GenerateCRUD/Postgres2_Spec.ts. Please confirm that this file exists and that it contains the correct test cases intended for the regression suite.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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=10

[github-actions]

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

[github-actions]

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/14026917130.
Cypress dashboard url: Click here!
All Cypress tests have passed 🎉🎉🎉

***** Repeat Run Summary ***** Total Tests with repeat: 170 Total Passed: 170 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.

[github-actions]

This PR has been closed because of inactivity.