appsmith icon indicating copy to clipboard operation
appsmith copied to clipboard
verified publisher icon appsmithorg

Do not merge : Run the test

Open sagar-qa007 opened this issue 1 year ago • 4 comments

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 #Issue Number
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="@tag.JSONForm"

:mag: Cypress test results

[!TIP] 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10736456751 Commit: 949b51ed40483b760ab050f7ed91c59ebbeb9ccc Cypress dashboard. Tags: @tag.JSONForm Spec:

Fri, 06 Sep 2024 10:28:19 UTC

Communication

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

  • [ ] Yes
  • [ ] No

Summary by CodeRabbit

  • Chores
    • Updated test specifications to prioritize testing of the "JSON Form" component with multiple source data.
    • Adjusted file references within the testing framework to reflect the new focus.

sagar-qa007 avatar Sep 06 '24 08:09 sagar-qa007

Walkthrough

The change involves updating the test specifications for Cypress limited tests, specifically replacing the test file for "Fork Template" with one focused on "JSON Form" functionality. This shift indicates a reallocation of testing priorities within the application while maintaining the overall structure of the test specification file.

Changes

File Changes Summary of Change
cypress/e2e/Regression/ClientSide/Templates/Fork_Template_spec.js Updated to cypress/e2e/Regression/ClientSide/Widgets/JSONForm/JSONForm_MultipleSourceData_spec.js to focus on JSON Form testing.

Poem

In the realm of code where tests reside,
A shift in focus, a new path to guide.
From Fork Template to JSON's embrace,
We celebrate change, a swift, elegant race.
With every test, our journey unfolds,
In the world of Cypress, new stories are told! 🌟

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

coderabbitai[bot] avatar Sep 06 '24 08:09 coderabbitai[bot]

/ci-test-limit-count run_count=20

sagar-qa007 avatar Sep 06 '24 08:09 sagar-qa007

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

github-actions[bot] avatar Sep 06 '24 08:09 github-actions[bot]

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10735457518. Cypress dashboard url: Click here! All cypress tests have passed 🎉🎉🎉

***** Repeat Run Summary ***** Total Tests with repeat: 140 Total Passed: 140 Total Failed: 0 Total Skipped: 0 *****************************

github-actions[bot] avatar Sep 06 '24 09:09 github-actions[bot]