chore: Skipping case due to Issue38156

[sagar-qa007]

Description

Skipping case due to : #38156

Fixes # #38156

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12746823242
Commit: ac771ea
Cypress dashboard.
Tags: @tag.Settings
Spec:

---

Mon, 13 Jan 2025 12:31:16 UTC

Communication

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

• Yes
• No

Summary by CodeRabbit

• Tests
  • Temporarily disabled a test suite for file upload testing
  • Skipped test suite due to known issue

[coderabbitai]

Walkthrough

This pull request involves modifying a Cypress end-to-end test file by using describe.skip() to temporarily disable a test suite for the API file upload functionality. The change suggests that there's a known issue preventing the test from running successfully, and the development team has chosen to skip the entire test suite until the underlying problem can be resolved.

Changes

File	Change Summary
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Bug_Upload_File_GreaterThan_20MB_spec.ts	Skipped entire test suite using describe.skip()

Possibly related PRs

• chore: Update RestApiDatasource_spec.js #38042: Similar test suite skipping in another file
• test: flaky check for published Spec #38427: Another instance of skipping a test suite
• test: flaky check for Abort spec #38428: Consistent approach to test suite skipping

Suggested Labels

skip-changelog, ok-to-test, Test

Suggested Reviewers

• ApekshaBhosale
• NandanAnantharamu

Poem

🧪 A test suite sleeps, quietly skipped
Waiting for bugs to be neatly clipped
Cypress whispers, "Not today, my friend"
Code pauses, a temporary suspend
Testing's rhythm, a momentary rest 🛌

---

📜 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 bfd66e5 and ac771ea.

📒 Files selected for processing (1)

• app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Bug_Upload_File_GreaterThan_20MB_spec.ts (1 hunks)

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

• app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Bug_Upload_File_GreaterThan_20MB_spec.ts

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

• GitHub Check: perform-test / rts-build / build
• GitHub Check: client-prettier / prettier-check
• GitHub Check: client-lint / client-lint
• GitHub Check: client-build / client-build

---

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