feat: add cypress tests for drag and drop building blocks

[jacquesikot]

Description

[!TIP]
Adds the following cypress tests suite and cases for building blocks drag and drop Building_Blocks.ts

• Building blocks tag is visible and open by default
• If widgets are more than 9, see more button should be visible
• Should not show the 'See More' button if widgets are less than 9
• Clicking on 'See More' button should show all widgets, and 'See Less' should show max 9 widgets

Fixes #32961

Automation

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

:mag: Cypress test results

[!TIP] 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9131833363 Commit: 07eaa5e8e92a2ac5fb740cd3646140d1b28ae468 Cypress dashboard url: Click here!

Communication

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

• [ ] Yes
• [x] No

Summary by CodeRabbit

• Tests
  • Introduced new tests for the Building Blocks explorer to ensure the visibility of tags, the functionality of "See More" and "See Less" buttons, and proper display behavior for widgets.

[coderabbitai[bot]]

Walkthrough

The changes focus on enhancing the drag-and-drop functionality for building blocks in the client-side application. This includes adding Cypress tests for automation, updating Redux actions and reducers to handle skeleton loaders, and modifying saga functions to manage widget additions and deletions. The updates ensure smoother interactions and better state management for building blocks.

Changes

Files/Modules	Change Summary
Drag_Drop_Building_Blocks_spec.ts	Added imports and constants for testing building blocks explorer functionality.
WidgetCard.tsx	Modified className assignment logic in WidgetCardComponent to include details.type and details.displayName.

Assessment against linked issues

Objective	Addressed	Explanation
Automation testing for drag and drop building blocks (Issue #32961)	✅
Ensure building blocks explorer functionality is covered (visibility, interaction, drag-drop)	✅
Update Redux actions and reducers to manage skeleton loaders effectively	✅
Modify saga functions to handle widget additions and deletions with skeleton loaders	✅

---

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>.
  • 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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[github-actions[bot]]

This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected.