chore: added test for asserting save button

[NilanshBansal]

Description

This PR adds asserts the Save button which was added in place of Save and Authorize in #32047
Fixes #32071

Automation

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

🔍 Cypress test results

Important

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

Summary by CodeRabbit

• Tests
  • Enhanced testing for GraphQL data sources by adding an assertion to verify the presence of a "Save" button for Client Credentials Grant Type scenarios.

[coderabbitai]

Walkthrough

Walkthrough

The change introduces a specific assertion within a Cypress end-to-end test for GraphQL data sources. This assertion checks for the presence of a "Save" button when configuring the Client Credentials Grant Type, ensuring that the user interface behaves as expected for this authentication method.

Changes

File Path	Change Summary
.../cypress/e2e/Sanity/Datasources/GraphQL_spec.ts	Added an assertion to verify the "Save" button's existence for Client Credentials Grant Type.

Assessment against linked issues

Objective	Addressed	Explanation
CI Test Case for OAuth2 Client Credentials Grant Type Save Button (#32071)	✅

Related issues

• [Task]: Fix cypress test suite failures caused by PR #29794 #30378: This issue discusses the need for addressing test failures caused by changes in a previous PR. While the current PR does not directly address test failures, it enhances the test suite by adding a new assertion. This indirectly contributes to the overall stability and coverage of the test suite, suggesting that it might be beneficial to link these issues for a broader context of maintaining test suite integrity post-changes.

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-tests 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 tests 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 tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[rohan-arthur]

Why are you running tag.all? Wouldn't it suffice to run say datasources ?