Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: Api curl remaining cases #38753

Merged
merged 2 commits into from
Jan 19, 2025
Merged

test: Api curl remaining cases #38753

merged 2 commits into from
Jan 19, 2025

Conversation

sagar-qa007
Copy link
Contributor

@sagar-qa007 sagar-qa007 commented Jan 18, 2025

Description

New test cases

Fixes # https://app.zenhub.com/workspaces/qa-63316faf86bb2e170ed2e46b/issues/gh/appsmithorg/appsmith/38478

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12850322339
Commit: 308c60e
Cypress dashboard.
Tags: @tag.Datasource
Spec:


Sun, 19 Jan 2025 09:01:49 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • Tests
    • Added comprehensive Cypress end-to-end tests for API panel functionality
    • Validated run button state with empty fields
    • Verified error handling for invalid URL inputs
    • Confirmed keyboard navigation for running API tests

Copy link
Contributor

coderabbitai bot commented Jan 18, 2025

Walkthrough

This pull request introduces a new Cypress end-to-end test file API_RunValidations_spec.ts for the API panel. The tests focus on validating three key scenarios: disabling the run button with empty fields, displaying error messages for invalid URLs, and verifying keyboard navigation (Cmd + Enter) functionality in the API panel.

Changes

File Change Summary
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts New test file added with three comprehensive API panel validation test cases

Sequence Diagram

sequenceDiagram
    participant User
    participant APIPanel
    participant RunButton
    
    User->>APIPanel: Enter API details
    alt Empty Fields
        APIPanel-->>RunButton: Disable Run Button
    end
    
    User->>APIPanel: Enter Invalid URL
    User->>APIPanel: Click Import
    APIPanel-->>User: Display Error Message
    
    User->>APIPanel: Focus on Data Source
    User->>APIPanel: Cmd + Enter
    APIPanel->>RunButton: Trigger Run
Loading

Possibly related PRs

  • fix: fix oracle spec #38435: This PR modifies tests related to the API Run button's disabled state, which is directly relevant to the functionality being validated in the main PR's Cypress tests for the API panel.
  • fix: Update for fix #38035: This PR focuses on refining test logic related to API error handling, which aligns with the main PR's tests that check for appropriate error messages when invalid inputs are provided in the API panel.
  • fix: Added login for better flow #38569: This PR enhances the test flow for admin settings, ensuring proper user session management, which may relate to the overall testing strategy in the main PR's context of API functionality validation.

Suggested labels

Task

Suggested reviewers

  • ApekshaBhosale
  • yatinappsmith

Poem

🧪 API tests dance with grace,
Validations run at lightning pace
Buttons click, errors shine bright
Cypress weaves tests with delight!
Quality code, our software's might 🚀


📜 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 a8b8177 and 308c60e.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: perform-test / client-build / client-build
  • GitHub Check: perform-test / rts-build / build
  • GitHub Check: perform-test / server-build / server-unit-tests
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-lint / client-lint
  • GitHub Check: client-build / client-build
  • GitHub Check: client-prettier / prettier-check

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

@sagar-qa007 sagar-qa007 added the ok-to-test Required label for CI label Jan 18, 2025
@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test labels Jan 18, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts (2)

9-12: Consider using a more descriptive test suite name.

The current description "API Panel request body" could be more specific about what aspects are being tested, e.g., "API Panel Run Button and URL Validation Tests".


13-16: Add more assertions for comprehensive validation.

While the test checks for button disability, consider adding assertions for:

  • Button state before API creation
  • Visual indicators of the disabled state
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 86bddaa and a8b8177.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: perform-test / rts-build / build
  • GitHub Check: perform-test / server-build / server-unit-tests
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-prettier / prettier-check
🔇 Additional comments (1)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_RunValidations_spec.ts (1)

1-8: LGTM! Clean imports following best practices.

Comment on lines +18 to +26
it('2. Validate we get an appropriate error message when an invalid URL is entered. Error should show up when nothing is entered & we click on "Import".', function () {
apiPage.CreateAndFillApi(
"htt://failedurlfortest",
"WhatTrumpThinks",
"SecondAPI",
);
agHelper.GetNClick(apiPage._apiRunBtn, 0, true, 10000);
apiPage.ResponseStatusCheck("PE-RST-5000");
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Replace GetNClick wait time with proper assertions.

The use of hardcoded wait time (10000) in GetNClick violates the Cypress best practices.

Replace with:

-      agHelper.GetNClick(apiPage._apiRunBtn, 0, true, 10000);
+      agHelper.GetNAssertElementPresence(apiPage._apiRunBtn)
+      agHelper.GetNClick(apiPage._apiRunBtn);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
it('2. Validate we get an appropriate error message when an invalid URL is entered. Error should show up when nothing is entered & we click on "Import".', function () {
apiPage.CreateAndFillApi(
"htt://failedurlfortest",
"WhatTrumpThinks",
"SecondAPI",
);
agHelper.GetNClick(apiPage._apiRunBtn, 0, true, 10000);
apiPage.ResponseStatusCheck("PE-RST-5000");
});
it('2. Validate we get an appropriate error message when an invalid URL is entered. Error should show up when nothing is entered & we click on "Import".', function () {
apiPage.CreateAndFillApi(
"htt://failedurlfortest",
"WhatTrumpThinks",
"SecondAPI",
);
agHelper.GetNAssertElementPresence(apiPage._apiRunBtn)
agHelper.GetNClick(apiPage._apiRunBtn);
apiPage.ResponseStatusCheck("PE-RST-5000");
});

Comment on lines 28 to 39
it("3. Validate keyboard navigation e.g. Cmd + Enter should trigger the Run button", function () {
apiPage.CreateAndFillApi(
dataManager.dsValues[dataManager.defaultEnviorment].randomTrumpApi,
"WhatTrumpThinks",
"ThirdAPI",
);
agHelper.GetNClick(ApiEditor.dataSourceField, 0, true);
cy.get(ApiEditor.dataSourceField).type("{cmd}{enter}", {
release: false,
});
assertHelper.AssertNetworkStatus("@postExecute");
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Improve cross-platform compatibility for keyboard shortcuts.

The current implementation might not work correctly across different operating systems.

Consider:

  1. Using a platform-agnostic approach
  2. Adding assertions for both Windows (Ctrl+Enter) and Mac (Cmd+Enter)
-      cy.get(ApiEditor.dataSourceField).type("{cmd}{enter}", {
+      cy.get(ApiEditor.dataSourceField).type(Cypress.platform === 'darwin' ? '{cmd}{enter}' : '{ctrl}{enter}', {
         release: false,
       });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
it("3. Validate keyboard navigation e.g. Cmd + Enter should trigger the Run button", function () {
apiPage.CreateAndFillApi(
dataManager.dsValues[dataManager.defaultEnviorment].randomTrumpApi,
"WhatTrumpThinks",
"ThirdAPI",
);
agHelper.GetNClick(ApiEditor.dataSourceField, 0, true);
cy.get(ApiEditor.dataSourceField).type("{cmd}{enter}", {
release: false,
});
assertHelper.AssertNetworkStatus("@postExecute");
});
it("3. Validate keyboard navigation e.g. Cmd + Enter should trigger the Run button", function () {
apiPage.CreateAndFillApi(
dataManager.dsValues[dataManager.defaultEnviorment].randomTrumpApi,
"WhatTrumpThinks",
"ThirdAPI",
);
agHelper.GetNClick(ApiEditor.dataSourceField, 0, true);
cy.get(ApiEditor.dataSourceField).type(Cypress.platform === 'darwin' ? '{cmd}{enter}' : '{ctrl}{enter}', {
release: false,
});
assertHelper.AssertNetworkStatus("@postExecute");
});

Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sagar-qa007 sagar-qa007 merged commit 2a2e37a into release Jan 19, 2025
45 checks passed
@sagar-qa007 sagar-qa007 deleted the test/apicurltestcases branch January 19, 2025 15:30
@coderabbitai coderabbitai bot mentioned this pull request Feb 6, 2025
2 tasks
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Feb 7, 2025
## Description
New test cases

Fixes #
https://app.zenhub.com/workspaces/qa-63316faf86bb2e170ed2e46b/issues/gh/appsmithorg/appsmith/38478

## Automation

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

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/12850322339>
> Commit: 308c60e
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=12850322339&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Datasource`
> Spec:
> <hr>Sun, 19 Jan 2025 09:01:49 UTC
<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Tests**
- Added comprehensive Cypress end-to-end tests for API panel
functionality
	- Validated run button state with empty fields
	- Verified error handling for invalid URL inputs
	- Confirmed keyboard navigation for running API tests
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants