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

[Donot merge]: testing cypress flakiness #35874

Closed
wants to merge 27 commits into from

Conversation

AmanAgarwal041
Copy link
Contributor

@AmanAgarwal041 AmanAgarwal041 commented Aug 26, 2024

Description

This PR fixes the cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts spec flakiness file.

  • Fixes the table index 17 to 12 to make it present in the viewport
  • Commented the deletion of an action in a page to enable the generate crud to create new page.

Fixes #35150
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=""

🔍 Cypress test results

Warning

Invalid tags. Please use /ok-to-test tags="@tag.All" or /test all in the PR body to run all tests.
Tags documentation.
List of valid tags.


Wed, 11 Sep 2024 08:52:39 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores
    • Updated test specifications to focus on server-side API and CRUD operations, enhancing the testing strategy to prioritize server functionalities.
  • Bug Fixes
    • Removed visibility assertion in the API page test interactions, simplifying the click action but introducing potential risks of runtime errors if elements are not visible.
  • Tests
    • Adjusted row indices in MySQL2 test specifications to align with changes in the underlying data structure and ensure accurate data assertions.
    • Introduced new multipart API testing logic, improving clarity and flexibility in API interactions.
    • Added search functionality in MongoDB test specifications to enhance data validation accuracy.
    • Enhanced CRUD page generation with dynamic query updates for improved flexibility.
    • Expanded test coverage by interacting with the table dropdown to validate multiple data entries effectively.
    • Introduced a new method for more precise targeting of table columns based on text content.
    • Streamlined network status assertions in MongoURI tests for improved efficiency and clarity.

Copy link
Contributor

coderabbitai bot commented Aug 26, 2024

Walkthrough

The changes involve significant updates to the Cypress testing framework, transitioning from client-side tests to server-side API and CRUD operations. The limited-tests.txt file has been revised to focus on server-side tests, while the ApiPage.ts class has simplified interactions by removing visibility checks. Additionally, specific row indices in the MySQL2_Spec.ts file have been adjusted to align with the updated data structure, and the Mongo_Spec.ts file has introduced new functions to enhance the testing of CRUD operations.

Changes

File Path Change Summary
app/client/cypress/limited-tests.txt Updated to replace client-side test references with new entries for server-side API and CRUD tests.
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts Adjusted row indices in test specifications to reflect changes in the underlying data structure.
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/Mongo_Spec.ts Introduced new functions for searching and updating queries, enhancing CRUD test coverage.
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_MultiPart_Spec.ts Replaced references to CloudinaryUploadApi with MultipartAPI, updating API interactions.
app/client/cypress/support/Pages/ApiPage.ts Removed visibility assertion before clicking UI elements, simplifying interaction.
app/client/cypress/support/Pages/Table.ts Added a new method for constructing selectors based on column data, improving table manipulation.

Assessment against linked issues

Objective Addressed Explanation
Fix flakiness of MySQL2_Spec.ts (35150)
Fix flakiness of API_MultiPart_Spec.ts (35137) Changes do not address the dependency on external API errors.
Fix flakiness of Mongo_Spec.ts (35149) Unclear if changes resolve the specific flakiness issues.
Fix flakiness of MongoURI_Spec.ts (35148) Unclear if changes resolve the specific flakiness issues.

Possibly related PRs

  • fix: flaky mongo spec test #36220: The changes in this PR involve modifications to the Mongo_Spec.ts file, which is directly related to the main PR's updates to the limited-tests.txt file that now includes Mongo_Spec.ts as a test specification.

Suggested labels

Bug, skip-changelog

Poem

In the realm of tests, a shift we see,
From client-side scripts to server's decree.
APIs and CRUD now take the stage,
In MongoDB and MySQL, we turn the page.
With every line, our strategy grows,
Testing the heart of the system that flows! 🌟


Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4da52dc and 52703b2.

Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MongoURI_Spec.ts (3 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MongoURI_Spec.ts

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

@github-actions github-actions bot added the Bug Something isn't working label Aug 26, 2024
@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9889117 and 276f28a.

Files selected for processing (1)
  • app/client/cypress/limited-tests.txt (1 hunks)
Additional context used
Path-based instructions (1)
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.
Additional comments not posted (4)
app/client/cypress/limited-tests.txt (4)

2-2: LGTM!

The test specification for API multipart handling is correctly added.

The code changes are approved.


3-3: LGTM!

The test specification for MongoDB CRUD operations is correctly added.

The code changes are approved.


4-4: LGTM!

The test specification for MongoDB URI CRUD operations is correctly added.

The code changes are approved.


5-5: LGTM!

The test specification for MySQL CRUD operations is correctly added.

The code changes are approved.

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 1

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 276f28a and ac60ca5.

Files selected for processing (1)
  • app/client/cypress/support/Pages/ApiPage.ts (1 hunks)
Additional context used
Path-based instructions (1)
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.

@@ -303,7 +303,7 @@ export class ApiPage {
| "RAW",
) {
this.agHelper.GetNClick(this._bodyTypeSelect);
cy.xpath(this._bodyTypeToSelect(subTabName)).should("be.visible").click();
this.agHelper.GetNClick(this._bodyTypeToSelect(subTabName));
Copy link
Contributor

Choose a reason for hiding this comment

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

Reintroduce visibility assertion or ensure element is interactable

The visibility assertion has been removed before clicking the element. This might lead to runtime errors if the element is not visible at the time of the click. Consider reintroducing the visibility assertion or ensuring the element is interactable before clicking it.

- this.agHelper.GetNClick(this._bodyTypeToSelect(subTabName));
+ cy.xpath(this._bodyTypeToSelect(subTabName)).should("be.visible");
+ this.agHelper.GetNClick(this._bodyTypeToSelect(subTabName));

Committable suggestion was skipped due to low confidence.

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ac60ca5 and 0cb3558.

Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts (1 hunks)
Additional context used
Path-based instructions (1)
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_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.
Additional comments not posted (4)
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts (4)

132-132: Verify the correctness of the new row index.

Ensure that the new row index 12 aligns with the intended data structure and that the correct data row is being selected.


133-133: Verify the correctness of the new row index.

Ensure that the new row index 12 aligns with the intended data structure and that the correct data row is being asserted.


134-134: Verify the correctness of the new row index.

Ensure that the new row index 12 aligns with the intended data structure and that the correct data row is being used to generate store secret information.


138-138: Verify the correctness of the new row index.

Ensure that the new row index 12 aligns with the intended data structure and that the correct data row is being updated and verified.

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0cb3558 and 46349b5.

Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 46349b5 and c1d3112.

Files selected for processing (2)
  • app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_MultiPart_Spec.ts (6 hunks)
  • app/client/cypress/support/Objects/DataManager.ts (2 hunks)
Additional context used
Path-based instructions (2)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_MultiPart_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.
app/client/cypress/support/Objects/DataManager.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.
Additional comments not posted (8)
app/client/cypress/e2e/Regression/ServerSide/ApiTests/API_MultiPart_Spec.ts (6)

5-5: Good job adding the import!

The dataManager import is necessary for accessing the multipartAPI property.


132-133: Great use of dynamic URL!

Using a dynamic URL from dataManager enhances flexibility and allows for different environments or configurations.


149-149: Good update on the success message!

Updating the success message to reflect the new API name ensures consistency in feedback during tests.


167-167: Nice update on the property field value!

Updating the property field value for the image upload to reference MultipartAPI.data.url aligns the test with the new API structure.


171-171: Good consistency in naming!

Ensuring that the API entity selection references MultipartAPI maintains consistency with the new naming convention.


219-219: Good update on the error message!

Updating the error message to reflect the new API name ensures consistency in feedback during tests.

app/client/cypress/support/Objects/DataManager.ts (2)

83-84: Great addition of multipartAPI property!

Adding the multipartAPI property to the Production environment enhances the functionality of the DataManager class by providing an endpoint specifically for multipart API interactions.


184-185: Great addition of multipartAPI property!

Adding the multipartAPI property to the Staging environment enhances the functionality of the DataManager class by providing an endpoint specifically for multipart API interactions.

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c1d3112 and 8a0bca2.

Files selected for processing (2)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts (2 hunks)
  • app/client/cypress/limited-tests.txt (1 hunks)
Files skipped from review as they are similar to previous changes (2)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts
  • app/client/cypress/limited-tests.txt

Copy link

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

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit runId=10593192904

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit-count run_count=5

Copy link

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit-count run_count=5 runId=10786510519

Copy link

Copy link

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

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

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

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: 0

Outside diff range, codebase verification and nitpick comments (1)
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MongoURI_Spec.ts (1)

144-155: Great job refactoring the network status assertions! This change improves code clarity and aligns with Cypress best practices.

A few notes:

  • Consolidating the assertions into a single cy.wait block that handles multiple interceptions enhances readability and efficiency. Well done!
  • Extracting the response statuses and asserting them using expect is a cleaner approach compared to the previous assertHelper method.
  • Consider removing the commented-out assertHelper.AssertNetworkStatus lines to keep the code clean, unless you plan to use them later for reference.

To remove the unused lines of code, apply this diff:

-      // assertHelper.AssertNetworkStatus("@postExecute", 200);
-      // assertHelper.AssertNetworkStatus("@postExecute", 200);
Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 506cec8 and 02e7f62.

Files selected for processing (2)
  • app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MongoURI_Spec.ts (1 hunks)
  • app/client/cypress/limited-tests.txt (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/limited-tests.txt
Additional context used
Path-based instructions (1)
app/client/cypress/e2e/Regression/ServerSide/GenerateCRUD/MongoURI_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.

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit runId=10791048104

Copy link

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit runId=10791048104

Copy link

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit

Copy link

@AmanAgarwal041
Copy link
Contributor Author

/ci-test-limit runId=10806018715

Copy link

Copy link

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

@AmanAgarwal041
Copy link
Contributor Author

All the flakiness prs are merged. Hence closing this one.

@AmanAgarwal041 AmanAgarwal041 deleted the cypress-test-limit branch September 17, 2024 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cypress-flaky-fix This label is auto-added when a PR which only has Cypress fixes are merged to release Integrations Pod General Issues related to the Integrations Pod that don't fit into other tags. Integrations Product Issues related to a specific integration ok-to-test Required label for CI Query & JS Pod Issues related to the query & JS Pod Stability Pod For all issues/tasks to be prioritized under Stability pod Task A simple Todo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task]: Fix flakiness of cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts
1 participant