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

chore: skipping cases for mockdb usage #38888

Merged
merged 2 commits into from
Jan 30, 2025
Merged

Conversation

sagar-qa007
Copy link
Contributor

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

Description

There were cases where mockdb is corrupt and we do see cypress failure. As it is not controlled by any of the team member to remain unchnaged, skipping test cases related to it.

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

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13028133245
Commit: 20e983d
Cypress dashboard.
Tags: @tag.All
Spec:


Wed, 29 Jan 2025 12:03:43 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • Tests
    • Skipped multiple test suites and individual test cases across various test specification files.
    • Temporarily disabled tests related to datasources, widget validation, mobile responsiveness, and CRUD operations.
    • Modifications made to prevent specific tests from running during test execution.

Copy link
Contributor

coderabbitai bot commented Jan 29, 2025

Walkthrough

This pull request involves systematically skipping multiple Cypress test suites and individual test cases across various specification files in the client-side testing directory. The changes primarily use the .skip() method on describe and it blocks, effectively preventing specific tests from running during test execution. These modifications suggest temporary disabling of tests, likely due to known issues or ongoing development work.

Changes

File Path Change Summary
app/client/cypress/e2e/Regression/ClientSide/BugTests/ Skipped tests in DS_Bug26716_Spec.ts and DS_Bug28750_Spec.ts
app/client/cypress/e2e/Regression/ClientSide/BugTests/DatasourceSchema_spec.ts Skipped two specific test cases about schema verification
app/client/cypress/e2e/Regression/ClientSide/Debugger/Widget_property_navigation_spec.ts Skipped "Table widget validation regex" test case
app/client/cypress/e2e/Regression/ClientSide/MobileResponsiveTests/ConversionFlow_Generated_App_spec.ts Skipped entire test suite for generated app conversion
app/client/cypress/e2e/Regression/ClientSide/OneClickBinding/PropertyControl_spec.ts Skipped datasource selector test case
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts Skipped "Query bottom bar should be collapsable" test
app/client/cypress/e2e/Regression/ServerSide/OnLoadTests/JSOnLoad_cyclic_dependency_errors_spec.js Skipped entire cyclic dependency test suite
app/client/cypress/e2e/Sanity/Datasources/ Skipped test suites in MockDBs_Spec.ts and Styles_spec.js
app/client/cypress/e2e/Smoke/GenerateCRUD/Generate_Crud_New_Page_spec.ts Skipped CRUD operation test suite

Possibly related PRs

Suggested Labels

Test

Suggested Reviewers

  • ApekshaBhosale
  • NandanAnantharamu
  • yatinappsmith

Poem

🧪 Tests on pause, a momentary rest
Skipping blocks with temporary zest
Cypress waits, no judgment passed
Bugs will hide, but not forever last
Code's silent symphony plays on! 🚀


📜 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 c6cfe0d and 20e983d.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ClientSide/OneClickBinding/PropertyControl_spec.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/e2e/Regression/ClientSide/OneClickBinding/PropertyControl_spec.ts
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: perform-test / rts-build / build
  • GitHub Check: perform-test / server-build / server-unit-tests
  • GitHub Check: perform-test / client-build / client-build
  • GitHub Check: client-lint / client-lint
  • GitHub Check: client-unit-tests / client-unit-tests
  • 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.

@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Jan 29, 2025
@sagar-qa007 sagar-qa007 added the ok-to-test Required label for CI label Jan 29, 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: 0

🧹 Nitpick comments (2)
app/client/cypress/e2e/Regression/ClientSide/BugTests/DatasourceSchema_spec.ts (1)

Line range hint 68-85: Approve skipping mockdb test but refactor sleep usage.

The decision to skip this test aligns with the PR objective of handling mockdb issues. However, when this test is re-enabled:

  1. Replace agHelper.Sleep with proper Cypress wait commands
  2. Consider using data-* attributes for selectors
- agHelper.Sleep(1500);
+ cy.waitUntil(() => {
+   return cy.get('[data-testid="schema-loaded"]').should('be.visible');
+ });
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts (1)

Line range hint 80-119: Consider consolidating duplicate test implementations.

While skipping the mockdb test aligns with PR objectives, there's a duplicate implementation of this test for airgap environments. Consider consolidating these tests using conditional logic.

- it.skip(
-   "5. Query bottom bar should be collapsable",
-   { tags: ["@tag.excludeForAirgap"] },
-   () => {
-     // ... test implementation
-   }
- );
- 
- it("airgap", "5. Query bottom bar should be collapsable - airgap", () => {
+ it(
+   "5. Query bottom bar should be collapsable",
+   { tags: ["@tag.excludeForAirgap"] },
+   () => {
+     if (Cypress.env("IS_AIRGAP")) {
+       // airgap implementation
+     } else {
+       // regular implementation
+     }
+   }
+ );
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1b352bb and c6cfe0d.

📒 Files selected for processing (11)
  • app/client/cypress/e2e/Regression/ClientSide/BugTests/DS_Bug26716_Spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/BugTests/DS_Bug28750_Spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/BugTests/DatasourceSchema_spec.ts (2 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/Debugger/Widget_property_navigation_spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/MobileResponsiveTests/ConversionFlow_Generated_App_spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/OneClickBinding/PropertyControl_spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ServerSide/OnLoadTests/JSOnLoad_cyclic_dependency_errors_spec.js (1 hunks)
  • app/client/cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts (1 hunks)
  • app/client/cypress/e2e/Sanity/Datasources/Styles_spec.js (1 hunks)
  • app/client/cypress/e2e/Smoke/GenerateCRUD/Generate_Crud_New_Page_spec.ts (1 hunks)
✅ Files skipped from review due to trivial changes (9)
  • app/client/cypress/e2e/Smoke/GenerateCRUD/Generate_Crud_New_Page_spec.ts
  • app/client/cypress/e2e/Regression/ClientSide/BugTests/DS_Bug28750_Spec.ts
  • app/client/cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts
  • app/client/cypress/e2e/Regression/ClientSide/MobileResponsiveTests/ConversionFlow_Generated_App_spec.ts
  • app/client/cypress/e2e/Regression/ClientSide/BugTests/DS_Bug26716_Spec.ts
  • app/client/cypress/e2e/Regression/ServerSide/OnLoadTests/JSOnLoad_cyclic_dependency_errors_spec.js
  • app/client/cypress/e2e/Sanity/Datasources/Styles_spec.js
  • app/client/cypress/e2e/Regression/ClientSide/Debugger/Widget_property_navigation_spec.ts
  • app/client/cypress/e2e/Regression/ClientSide/OneClickBinding/PropertyControl_spec.ts
🧰 Additional context used
📓 Path-based instructions (2)
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_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/e2e/Regression/ClientSide/BugTests/DatasourceSchema_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: build
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-prettier / prettier-check
  • GitHub Check: client-build / client-build
🔇 Additional comments (1)
app/client/cypress/e2e/Regression/ClientSide/BugTests/DatasourceSchema_spec.ts (1)

Line range hint 86-102: Approve skipping mockdb test.

The decision to skip this test aligns with the PR objective of handling mockdb-related test failures.

@sagar-qa007 sagar-qa007 merged commit 2dbf810 into release Jan 30, 2025
85 checks passed
@sagar-qa007 sagar-qa007 deleted the chore/skipmockdbspec branch January 30, 2025 06:17
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Feb 7, 2025
## Description
There were cases where mockdb is corrupt and we do see cypress failure.
As it is not controlled by any of the team member to remain unchnaged,
skipping test cases related to it.


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

## Automation

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

### 🔍 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/13028133245>
> Commit: 20e983d
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=13028133245&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Wed, 29 Jan 2025 12:03:43 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**
- Skipped multiple test suites and individual test cases across various
test specification files.
- Temporarily disabled tests related to datasources, widget validation,
mobile responsiveness, and CRUD operations.
- Modifications made to prevent specific tests from running during test
execution.
<!-- 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants