test: fix test in airgap for canvas context prop

[NandanAnantharamu]

This test spec was working fine on EE/CE this fix will handle scenario in airgap environment

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

Tip

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

---

Wed, 25 Sep 2024 05:41:09 UTC

[coderabbitai]

Walkthrough

The pull request introduces modifications to the Canvas_Context_Property_Pane_1_spec.js test suite by implementing a conditional check for the AIRGAPPED environment variable, affecting the propertySectionState object. Additionally, it updates the limited-tests.txt configuration to replace a test file entry, thereby altering the set of tests executed under limited conditions.

Changes

File(s)	Change Summary
app/client/cypress/e2e/Regression/ClientSide/IDE/Canvas_Context_Property_Pane_1_spec.js	Introduced a conditional check for the AIRGAPPED environment variable affecting propertySectionState.
app/client/cypress/limited-tests.txt	Updated the test file entry from Fork_Template_spec.js to Canvas_Context_Property_Pane_1_spec.js.

Possibly related PRs

• test: fix canvas context property pane #36356: Modifies the logic for verifying the state of property pane sections, similar to changes in the propertySectionState object.
• test:Fix canvas context prop01 #36391: Enhances the verification process for property pane sections, directly relating to modifications in the Canvas_Context_Property_Pane_1_spec.js file.

Suggested labels

skip-changelog, ok-to-test, Test

Suggested reviewers

• ApekshaBhosale
• sagar-qa007

🌟 In the realm of tests, a change did appear,
With conditions set, our path is now clear.
The canvas awaits, with properties to define,
In limited runs, our tests will align.
So here's to the code, both clever and bright,
May our tests pass with joy, in the day and the night! 🌙

---

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 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=25

[github-actions]

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

[github-actions]

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