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

fix : Updating EntityBottomBar_spec.ts with a query which doesnt depe… #38057

Closed
wants to merge 1 commit into from

Conversation

trishaanand
Copy link
Contributor

@trishaanand trishaanand commented Dec 9, 2024

…nd on the field id

The data for mock db keeps changing. Removing dependency on id field to ensure that we fail less often. This is a temporary fix while we move away from external dependency of mockdb

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
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

/test IDE

🔍 Cypress test results

Tip

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


Mon, 09 Dec 2024 14:48:21 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • Tests
    • Updated test cases for the bottom bar functionality to ensure correct behavior across various components.
    • Modified SQL query in the last test case to adjust expected output.

@trishaanand trishaanand added the ok-to-test Required label for CI label Dec 9, 2024
Copy link
Contributor

coderabbitai bot commented Dec 9, 2024

Walkthrough

The changes in this pull request involve modifications to the test cases within the EntityBottomBar_spec.ts file. The primary alteration is a change in the SQL query string used in one of the test cases. The query was simplified from "SELECT * FROM users ORDER BY id LIMIT 10;" to "SELECT * FROM users LIMIT 10;", impacting the expected output without altering the overall structure or flow of the tests. The tests continue to verify the functionality of the bottom bar across various components.

Changes

File Change Summary
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts Modified SQL query string in the last test case, affecting expected output while maintaining test logic.

Possibly related PRs

Suggested labels

Bug, Test

Suggested reviewers

  • ApekshaBhosale
  • NandanAnantharamu
  • sagar-qa007

🎉 In the realm of code, a tweak so slight,
A query refined, now shining bright.
The bottom bar dances, with tests that align,
In the world of UI, everything's fine!
With each click and each tap, we verify,
Ensuring our features reach for the sky! 🌟


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

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 and nitpick comments (2)
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts (2)

Line range hint 77-77: Remove _.agHelper.Sleep() usage

Replace Sleep with proper Cypress wait commands that wait for specific conditions rather than arbitrary timeouts.

- _.agHelper.Sleep(1000);
+ cy.wait("@postExecute").its("response.statusCode").should("eq", 200);

Line range hint 156-158: Improve type safety in alias handling

Avoid using 'as any' type assertion. Instead, properly type the alias value.

- cy.get("@dsName").then(($dsName) => {
-   _.dataSources.DeleteDatasourceFromWithinDS($dsName as any);
- });
+ cy.get<string>("@dsName").then((dsName) => {
+   _.dataSources.DeleteDatasourceFromWithinDS(dsName);
+ });
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ab06288 and e1b7902.

📒 Files selected for processing (1)
  • app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
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.
🔇 Additional comments (2)
app/client/cypress/e2e/Regression/ClientSide/OtherUIFeatures/EntityBottomBar_spec.ts (2)

Line range hint 8-162: Well-structured test cases

The test cases follow good practices:

  • Multiple assertions are used
  • No it.only or after/afterEach hooks
  • Logical flow of test steps

143-143: Query change aligns with PR objectives

The removal of ORDER BY id makes the test more resilient by eliminating dependency on the 'id' field, which addresses the issue of test failures due to mock database changes.

Copy link

This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected.

@github-actions github-actions bot added the Stale label Dec 16, 2024
Copy link

This PR has been closed because of inactivity.

@github-actions github-actions bot closed this Dec 24, 2024
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 Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant