chore: skip long tests

[KelvinOm]

Description

Need to unblock client unit tests pipline.

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 select tests for IDE rendering features to streamline our testing process without impacting user-facing functionality.

[coderabbitai]

Walkthrough

The pull request disables two test suites by changing their declarations from describe to describe.skip, ensuring that the tests within these suites are not executed. In one case an ESLint comment is added to bypass the warning for disabled tests. No changes are made to the actual test logic or functionality.

Changes

File(s)	Change Summary
app/client/src/pages/AppIDE/layouts/routers/JSEditor/JSRender.test.tsx app/client/src/pages/AppIDE/layouts/routers/QueryEditor/QueryRender.test.tsx	Disabled test suites by replacing describe with describe.skip. In JSRender.test.tsx, an ESLint disable comment (// eslint-disable-next-line jest/no-disabled-tests) was added to prevent warnings.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as Test Runner
    participant JSEditor as JS Render Suite
    participant QueryEditor as Query Render Suite

    Runner->>JSEditor: Load test suite
    Note over JSEditor: Skipped (describe.skip)
    Runner->>QueryEditor: Load test suite
    Note over QueryEditor: Skipped (describe.skip)

Loading

Possibly related PRs

• chore: Skip case due to open bug #38930: Involves skipping tests using describe.skip or it.skip, similar to the changes in this PR.
• chore: Skipping case due to Issue38156 #38628: Also modifies test suites by disabling them with describe.skip, aligning with the approach used here.

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• ApekshaBhosale
• NandanAnantharamu

Poem

In the realm of tests where code does hide,
A skip was cast with a gentle guide.
No more running, a silent reprieve,
As ESLint sleeps and warnings leave.
🎉 Cheers to a pause in the test ride!

Happy skipping!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 472edcf and 272ad08.

📒 Files selected for processing (2)

• app/client/src/pages/AppIDE/layouts/routers/JSEditor/JSRender.test.tsx (1 hunks)
• app/client/src/pages/AppIDE/layouts/routers/QueryEditor/QueryRender.test.tsx (1 hunks)

⏰ 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-check-cyclic-deps / check-cyclic-dependencies
• GitHub Check: client-prettier / prettier-check

🔇 Additional comments (2)

app/client/src/pages/AppIDE/layouts/routers/QueryEditor/QueryRender.test.tsx (1)

18-19: Intentional Test Skipping with ESLint Directive
The test suite for "IDE URL rendering of Queries" is now intentionally skipped using describe.skip and is accompanied by an ESLint disable comment to bypass the jest/no-disabled-tests rule. This change meets the PR objective to unblock the pipeline by preventing long test executions.

app/client/src/pages/AppIDE/layouts/routers/JSEditor/JSRender.test.tsx (1)

14-15: JS Test Suite Skipping for Pipeline Unblocking
The "IDE Render: JS" test suite is now skipped via describe.skip, with an added ESLint disable comment. This approach effectively prevents these long-running tests from executing, aligning with the PR objective.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.