test: Editor tests for renaming, copying, moving, and deleting APIs #38896
Conversation
shadabbuchh
requested review from
ApekshaBhosale and
sagar-qa007
as code owners
WalkthroughThis pull request enhances API testing capabilities in the Cypress testing framework by introducing a comprehensive test suite for API management functionalities. The changes include new methods in the Changes
Sequence DiagramsequenceDiagram
participant User
participant APIEditor
participant PageManager
User->>APIEditor: Rename API
User->>APIEditor: Copy/Move API
APIEditor->>PageManager: Validate Page Transition
User->>APIEditor: Delete API
APIEditor->>PageManager: Confirm Deletion
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
github-actions
bot
added
skip-changelog
|
/ci-test-limit-count run_count=20 update_snapshot=true specs_to_run=cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts |
|
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/13030488733. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (3)
app/client/cypress/support/Pages/IDE/FileTabs.ts (1)
39-43: LGTM! Consider adding a custom error message.The assertion chain is well structured. For better debugging, you could include a custom error message in the assertion.
assertActiveTab(expectedTabName: string) { cy.get(this.locators.tabName(expectedTabName)) .should("exist") - .and("have.class", "active"); + .and("have.class", "active", `Tab ${expectedTabName} should be active`); }app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts (1)
67-81: Consider adding cleanup in beforeEach hook.The test assumes a clean state with specific API tabs. Consider adding cleanup in a beforeEach hook for better test isolation.
app/client/cypress/support/Pages/ApiPage.ts (1)
518-525: Consider adding retry logic for rename operation.The rename operation might be flaky due to UI state transitions. Consider adding retry logic for better stability.
public renameFromEditor(renameVal: string) { cy.get(this.moreActionsTrigger).click(); - cy.contains("Rename").should("be.visible").click(); + cy.contains("Rename", { timeout: 10000 }) + .should("be.visible") + .click();
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts(1 hunks)app/client/cypress/limited-tests.txt(1 hunks)app/client/cypress/support/Pages/ApiPage.ts(4 hunks)app/client/cypress/support/Pages/IDE/FileTabs.ts(1 hunks)app/client/cypress/support/Pages/PageList.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
app/client/cypress/support/Pages/PageList.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.
app/client/cypress/support/Pages/IDE/FileTabs.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.
app/client/cypress/limited-tests.txt (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.
app/client/cypress/support/Pages/ApiPage.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.
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_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: client-unit-tests / client-unit-tests
- GitHub Check: client-lint / client-lint
- GitHub Check: client-build / client-build
- GitHub Check: client-prettier / prettier-check
🔇 Additional comments (4)
app/client/cypress/support/Pages/PageList.ts (1)
19-19: LGTM! Selector follows established patterns.The new selector follows the existing pattern and uses data-testid attributes as recommended.
app/client/cypress/support/Pages/ApiPage.ts (1)
592-609: LGTM! Deletion flow is well implemented.The deletion method follows a clear flow with proper assertions and confirmations.
app/client/cypress/limited-tests.txt (2)
2-2: LGTM! Test specification follows naming conventions.The new test file path correctly follows TypeScript naming conventions and is appropriately placed in the ServerSide/ApiTests directory.
4-5: Configuration changes align with limited test execution.The changes appropriately restrict test execution to focus on API tests by:
- Keeping the all-specs execution commented out
- Excluding the Widgets test path
| it("3. Validate whether correct tab opens up after clicking on link from logs", () => { | ||
| // Create a new application | ||
| homePage.NavigateToHome(); | ||
| homePage.CreateNewApplication(); | ||
| for (let i = 0; i < 4; i++) { | ||
| apiPage.CreateApi(``, "GET"); | ||
| } | ||
| debuggerHelper.OpenDebugger(); | ||
| //Navigate to the "Logs" tab in the debugger | ||
| debuggerHelper.ClickLogsTab(); | ||
| // Click on the entity link in the log entry at index 2 | ||
| debuggerHelper.ClicklogEntityLink(false, 2); | ||
| // Assert that the correct tab ("Api3") opens | ||
| FileTabs.assertActiveTab("Api3"); | ||
| }); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Improve test isolation and avoid hardcoded indices.
The test relies on hardcoded index (2) for log entry selection, which could make the test brittle.
- debuggerHelper.ClicklogEntityLink(false, 2);
+ const LOG_INDEX = 2;
+ debuggerHelper.ClicklogEntityLink(false, LOG_INDEX);📝 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.
| it("3. Validate whether correct tab opens up after clicking on link from logs", () => { | |
| // Create a new application | |
| homePage.NavigateToHome(); | |
| homePage.CreateNewApplication(); | |
| for (let i = 0; i < 4; i++) { | |
| apiPage.CreateApi(``, "GET"); | |
| } | |
| debuggerHelper.OpenDebugger(); | |
| //Navigate to the "Logs" tab in the debugger | |
| debuggerHelper.ClickLogsTab(); | |
| // Click on the entity link in the log entry at index 2 | |
| debuggerHelper.ClicklogEntityLink(false, 2); | |
| // Assert that the correct tab ("Api3") opens | |
| FileTabs.assertActiveTab("Api3"); | |
| }); | |
| it("3. Validate whether correct tab opens up after clicking on link from logs", () => { | |
| // Create a new application | |
| homePage.NavigateToHome(); | |
| homePage.CreateNewApplication(); | |
| for (let i = 0; i < 4; i++) { | |
| apiPage.CreateApi(``, "GET"); | |
| } | |
| debuggerHelper.OpenDebugger(); | |
| //Navigate to the "Logs" tab in the debugger | |
| debuggerHelper.ClickLogsTab(); | |
| // Click on the entity link in the log entry at index 2 | |
| const LOG_INDEX = 2; | |
| debuggerHelper.ClicklogEntityLink(false, LOG_INDEX); | |
| // Assert that the correct tab ("Api3") opens | |
| FileTabs.assertActiveTab("Api3"); | |
| }); |
| it("1. Validate renaming & copying API from editor", () => { | ||
| // Create first API | ||
| apiPage.CreateApi(); | ||
| // Rename the API | ||
| apiPage.renameFromEditor("changedName"); | ||
| // Create second API | ||
| apiPage.CreateApi("secondApi", "GET"); | ||
| // Add a new blank page to the application | ||
| PageList.AddNewPage("New blank page"); | ||
| // Copy the API to the same page | ||
| apiPage.performActionFromEditor("copy", "changedName", "Page1", "Page1"); | ||
| // Copy the API to a different page | ||
| apiPage.performActionFromEditor("copy", "secondApi", "Page1", "Page2"); | ||
| }); |
There was a problem hiding this comment.
💡 Codebase verification
Add PageLeftPane assertions after API copy operations
Add the following verifications:
- After copying "changedName" API within Page1:
PageLeftPane.assertPresence("changedName"); PageLeftPane.assertPresence("changedName_Copy");
- After copying "secondApi" to Page2:
PageLeftPane.assertPresence("secondApi"); PageLeftPane.assertPresence("secondApi_Copy");
🔗 Analysis chain
Add assertions for API presence after copy operations.
The test should verify that the copied API exists in both source and target pages.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify the presence of API-related assertions in the test file
rg -A 2 "assertPresence.*Api" app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts
Length of output: 114
Script:
#!/bin/bash
# Search for any assertions in the test file
rg "expect|should|assert" app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts
# Look for apiPage method implementations
ast-grep --pattern 'apiPage.$_($$$)' app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts
# Search for verification methods in apiPage definition
fd -e ts -e js apiPage
Length of output: 2086
Script:
#!/bin/bash
# Search for apiPage class implementation
fd -t f -e ts -e js -H -I "apiPage" app/client/cypress/
# Search for performActionFromEditor implementation
rg -A 5 "performActionFromEditor.*{" app/client/cypress/
Length of output: 230
Script:
#!/bin/bash
# Search for performActionFromEditor implementation with fixed pattern
rg -A 5 "performActionFromEditor" app/client/cypress/
# Search for any verification methods in apiPage
rg -A 5 "verify.*Api|assert.*Api" app/client/cypress/
Length of output: 13943
| public performActionFromEditor( | ||
| action: "copy" | "move", | ||
| apiName: string, | ||
| sourcePage: string, | ||
| targetPage: string, | ||
| ) { | ||
| // Navigate to the source page and select the API item | ||
| EditorNavigation.NavigateToPage(sourcePage); | ||
| PageLeftPane.selectItem(apiName); | ||
| FileTabs.assertActiveTab(apiName); | ||
|
|
||
| PageList.ShowList(); | ||
| cy.get(PageList.numberOfPages).then(($el) => { | ||
| // Open the 'More Actions' menu and select the action | ||
| cy.get(this.moreActionsTrigger).should("be.visible").click(); // Open the 'More Actions' dropdown | ||
| cy.contains(action === "copy" ? "Copy to page" : "Move to page") | ||
| .should("be.visible") | ||
| .trigger("click", { force: true }); | ||
| if (action === "move" && $el.text().includes("All Pages (1)")) { | ||
| // Handle case where the target page list is empty during move operation | ||
| cy.get(this.pageList).should("have.text", "No pages"); | ||
| } else if (action === "move" && /All Pages \(\d+\)/.test($el.text())) { | ||
| cy.get(this.pageList) | ||
| .should("be.visible") | ||
| .should("not.have.text", sourcePage) | ||
| .contains(targetPage) | ||
| .should("be.visible") | ||
| .trigger("click", { force: true }); | ||
|
|
||
| this.agHelper.ValidateToastMessage( | ||
| apiName + " action moved to page " + targetPage + " successfully", | ||
| ); | ||
| PageList.VerifyIsCurrentPage(targetPage); // Verify the target page is active | ||
| PageLeftPane.assertPresence(apiName); // Assert the API is present on the target page | ||
| EditorNavigation.NavigateToPage(sourcePage); | ||
| PageLeftPane.assertAbsence(apiName); // Assert the API is removed from the source page | ||
| } else { | ||
| // Select the target page from the page list | ||
| cy.get(this.pageList) | ||
| .should("be.visible") | ||
| .contains(targetPage) | ||
| .should("be.visible") | ||
| .trigger("click", { force: true }); | ||
|
|
||
| // Validate the toast message and the current page | ||
| this.agHelper.ValidateToastMessage( | ||
| `${apiName} action ${action === "copy" ? "copied" : "moved"} to page ${targetPage} successfully`, | ||
| ); | ||
| PageList.VerifyIsCurrentPage(targetPage); // Verify the target page is active | ||
|
|
||
| // Assert the presence of the API on the target page | ||
| apiName = | ||
| action === "copy" && sourcePage === targetPage | ||
| ? `${apiName}Copy` | ||
| : apiName; | ||
| PageLeftPane.assertPresence(apiName); | ||
|
|
||
| if (action === "move") { | ||
| EditorNavigation.NavigateToPage(sourcePage); | ||
| PageLeftPane.assertAbsence(apiName); // Assert the API is removed from the source page | ||
| } | ||
| } | ||
| }); | ||
| } |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Refactor complex conditional logic in performActionFromEditor.
The method has complex nested conditions. Consider extracting the page list handling logic into separate methods.
+ private handleSinglePageMove(apiName: string, sourcePage: string) {
+ cy.get(this.pageList).should("have.text", "No pages");
+ }
+
+ private handleMultiPageMove(apiName: string, sourcePage: string, targetPage: string) {
+ cy.get(this.pageList)
+ .should("be.visible")
+ .should("not.have.text", sourcePage)
+ .contains(targetPage)
+ .should("be.visible")
+ .trigger("click", { force: true });
+ }Committable suggestion skipped: line range outside the PR's diff.
|
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13030488733. |
shadabbuchh
added
ok-to-test
|
|
||
| // Open the 'More Actions' menu and select the action | ||
| cy.get(this.moreActionsTrigger).should("be.visible").click(); | ||
| cy.contains("Delete") |
There was a problem hiding this comment.
Can we please use aghelper functions here?
Please apply same for all the cy commands.
| @@ -36,6 +36,12 @@ class FileTabs { | |||
| }); | |||
| } | |||
|
|
|||
| assertActiveTab(expectedTabName: string) { | |||
There was a problem hiding this comment.
Please use aghelper function.
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts (2)
54-56: Replace magic number with named constant.Define the number of APIs as a constant for better maintainability:
const NUM_TEST_APIS = 4; for (let i = 0; i < NUM_TEST_APIS; i++) { apiPage.CreateApi(`TestApi${i + 1}`, "GET"); }
68-70: Replace magic numbers with named constants.Define the range of API numbers as constants:
const FIRST_API_NUM = 1; const LAST_API_NUM = 4; for (let i = FIRST_API_NUM; i <= LAST_API_NUM; i++) { FileTabs.closeTab(`Api${i}`); }
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts(1 hunks)app/client/cypress/support/Pages/ApiPage.ts(4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- app/client/cypress/support/Pages/ApiPage.ts
🧰 Additional context used
📓 Path-based instructions (1)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_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 (7)
- GitHub Check: perform-test / rts-build / build
- GitHub Check: perform-test / client-build / client-build
- GitHub Check: perform-test / server-build / server-unit-tests
- GitHub Check: client-build / client-build
- GitHub Check: client-unit-tests / client-unit-tests
- GitHub Check: client-lint / client-lint
- GitHub Check: client-prettier / prettier-check
🔇 Additional comments (3)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_Additional_Tests_spec.ts (3)
1-12: LGTM! Well-organized imports.The imports are logically grouped and all are being used in the test suite.
14-17: LGTM! Well-structured test suite declaration.Good use of tags for categorizing tests under Datasource and Git categories.
18-31: Add PageLeftPane assertions after API copy operations.Add assertions to verify the presence of both original and copied APIs:
// After copying "changedName" API within Page1 PageLeftPane.assertPresence("changedName"); PageLeftPane.assertPresence("changedName_Copy"); // After copying "secondApi" to Page2 PageLeftPane.assertPresence("secondApi"); PageLeftPane.assertPresence("secondApi_Copy");
| it("2. Validate moving & deleting API from editor", () => { | ||
| // Create a new application | ||
| homePage.NavigateToHome(); | ||
| homePage.CreateNewApplication(); | ||
| // Create first API | ||
| apiPage.CreateApi("ApiToBeMoved", "GET"); | ||
| apiPage.CreateApi("ApiNotToBeMoved", "GET"); | ||
| // Having only one page in the app, check if the API is moved to the same page | ||
| apiPage.performActionFromEditor("move", "ApiToBeMoved", "Page1", "Page1"); | ||
| // Add a new blank page to the application | ||
| PageList.AddNewPage("New blank page"); | ||
| // Move the API to a different page & check if the source page does not have the API anymore | ||
| apiPage.performActionFromEditor("move", "ApiToBeMoved", "Page1", "Page2"); | ||
| apiPage.performActionFromEditor("move", "ApiToBeMoved", "Page2", "Page1"); | ||
| apiPage.deleteAPIFromEditor("ApiToBeMoved", "Page1"); | ||
| }); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add assertions to verify API move and delete operations.
Add assertions after each operation to verify the expected state:
// After moving API within same page
PageLeftPane.assertPresence("ApiToBeMoved");
// After moving API to different page
PageLeftPane.assertNotPresence("ApiToBeMoved", "Page1");
PageLeftPane.assertPresence("ApiToBeMoved", "Page2");
// After deleting API
PageLeftPane.assertNotPresence("ApiToBeMoved", "Page1");| debuggerHelper.ClicklogEntityLink(false, 2); | ||
| // Assert that the correct tab ("Api3") opens | ||
| agHelper.AssertClassExists(FileTabs.locators.tabName("Api3"), "active"); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Avoid hardcoded index in log selection.
The test relies on a hardcoded index (2) which makes it brittle. Consider using a more reliable way to identify the correct log entry, such as searching for specific content or using test data attributes.
| debuggerHelper.ClicklogEntityLink(false, 1); | ||
| // Assert that the correct tab ("Api2") reopens | ||
| agHelper.AssertClassExists(FileTabs.locators.tabName("Api2"), "active"); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Avoid hardcoded index in log selection.
Similar to the previous test, using a hardcoded index (1) makes the test brittle. Consider a more reliable way to identify the correct log entry.
Description
This PR adds set of tests for API-related operations in the editor, including renaming, copying, moving, and validating tab behaviors triggered from debugger logs.
Automation
/ok-to-test tags="@tag.Datasource, @tag.Git, @tag.Sanity"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13047527270
Commit: 09e3929
Cypress dashboard.
Tags:
@tag.Datasource, @tag.Git, @tag.SanitySpec:
Thu, 30 Jan 2025 08:38:58 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit
Release Notes
New Features
Tests
These updates improve the testing infrastructure and validate key API management features in the application.