Update MockDBs_Spec.ts

[johaankjis]

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes ##38889
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Tests
  • Temporarily disabled two test cases for Mock Postgres and Mock Mongo database queries
  • These test cases have been marked to be skipped during test runs

[coderabbitai]

Walkthrough

The pull request involves modifying the MockDBs_Spec.ts Cypress test file by skipping two specific test cases related to creating queries from Mock Postgres and Mongo databases. These tests, which previously verified active queries count, have been temporarily disabled using the .skip() method, effectively preventing them from running during test execution.

Changes

File	Change Summary
app/client/cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts	Skipped two test cases for Mock Postgres and Mongo DB query creation and active queries count verification

Possibly related issues

• [Task]: Fix flakiness of cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts #35136: Addresses the task of fixing flakiness in the MockDBs_Spec.ts test file, specifically for the Mock Mongo DB query test case

Possibly related PRs

• chore: Updated the mockdb code #38603: Modifies the same MockDBs_Spec.ts file by commenting out assertions related to active queries count verification

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

Poem

🧪 Cypress tests take a pause,
Skipping queries with gentle cause
Mock DBs rest, no assertions fly
Debugging magic from the sky!
Silence speaks where code once sang 🤫

---

📜 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 3ab237d and 40f61dd.

📒 Files selected for processing (1)

• app/client/cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• app/client/cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts

---

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.