test: to check postgres spec

[NandanAnantharamu]

/ok-to-test tags="@tag.Datasource"

Caution

🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13692798075
Commit: 500ec89
Cypress dashboard.
Tags: @tag.Datasource
Spec:
The following are new failures, please fix them before merging the PR:

1. cypress/e2e/Regression/ServerSide/GenerateCRUD/Postgres2_Spec.ts

List of identified flaky tests.

---

Thu, 06 Mar 2025 07:50:25 UTC

[coderabbitai]

Walkthrough

This PR updates the Cypress test configuration file by modifying the test specification paths in limited-tests.txt. A new server-side TypeScript test has been added, an existing commented-out visual test has been removed, and a previously active client-side widget test has now been commented out. These changes adjust which tests are executed during limited-test runs.

Changes

File	Change Summary
app/.../limited-tests.txt	- Removed: #cypress/e2e/Regression/ClientSide/VisualTests/JSEditorIndent_spec.js - Added: cypress/e2e/Regression/ServerSide/GenerateCRUD/Postgres2_Spec.ts - Commented: cypress/e2e/Regression/ClientSide/Anvil/Widgets/*

Possibly related PRs

• test: Skipping one test in API Edit Spec for functional bugs #38115: Updates test specification paths in limited-tests.txt, similar to the modifications in this PR.
• test: flaky check for onload spec #38429: Replaces a JavaScript test path with TypeScript test paths in limited-tests.txt, directly aligning with these changes.
• test: adding tests for custom lib #37901: Modifies limited-tests.txt by substituting a JavaScript test specification with a TypeScript one, indicating a direct code-level relationship.

Suggested labels

skip-changelog, ok-to-test, Test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

Poem

In the realm of tests, a change unfolds,
Paths refined as new code beholds.
Visuals retired, widgets in rest,
Server tests now stand the test.
Code flows anew with a subtle zest!
🚀✨

---

📜 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 defc0a9 and 500ec89.

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

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

• 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: Active Postgres Test Spec Added
The addition of the server-side test specification cypress/e2e/Regression/ServerSide/GenerateCRUD/Postgres2_Spec.ts aligns with the PR objective and appears correct. Just ensure that the corresponding test file follows the Cypress best practices (e.g., use of data-* attributes, API-driven login/logout) as outlined in our coding guidelines.

---

5-5: Client-Side Widget Tests Commented Out
Commenting out cypress/e2e/Regression/ClientSide/Anvil/Widgets/* looks intentional to temporarily disable these tests. Confirm that these widget tests are not required for the current limited-test run, and ensure their status is tracked if they need reactivation in the future.

---

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/13692634310.
Cypress dashboard
PR: #39588 .

[github-actions]

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