-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: fixed skipped graphQL test #35571
Conversation
Sure! Let’s go through this in a structured manner. WalkthroughThe recent changes reactivated a previously skipped test case in the Cypress test suite, focusing on a GraphQL binding issue. This update improves the clarity and functionality of the test by optimizing the logic and removing unnecessary elements. Overall, these changes ensure that the test actively validates the resolution of the identified bug, thereby enhancing the robustness of the testing framework. Changes
Assessment against linked issues
This format presents the changes effectively while celebrating the effort involved. If you have any further questions or need more information, feel free to ask! 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 as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
/ci-test-limit |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10316852912. |
There was a problem hiding this 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 (2)
app/client/cypress/e2e/Regression/ClientSide/BugTests/GraphQL_Binding_Bug16702_Spec.ts (2)
44-48
: Use locator variables instead of plain strings.The selector
.t--graphql-query-editor pre.CodeMirror-line span
is used directly. It's a good practice to use locator variables for maintainability and readability.- cy.get(".t--graphql-query-editor pre.CodeMirror-line span") + cy.get(_.locators._graphqlQueryEditorSpan)Make sure to define
_.locators._graphqlQueryEditorSpan
in your locators file.
58-62
: Ensure multiple assertions for robustness.The test checks for the autocomplete menu. Consider adding more assertions to verify other aspects of the UI or data state to ensure comprehensive validation.
// Example: Add assertions to check the presence of the autocomplete menu cy.get(_.locators._hints).should('be.visible');This will help ensure the test is robust and covers more scenarios.
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (1)
- app/client/cypress/e2e/Regression/ClientSide/BugTests/GraphQL_Binding_Bug16702_Spec.ts (3 hunks)
Additional context used
Path-based instructions (1)
app/client/cypress/e2e/Regression/ClientSide/BugTests/GraphQL_Binding_Bug16702_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 (1)
app/client/cypress/e2e/Regression/ClientSide/BugTests/GraphQL_Binding_Bug16702_Spec.ts (1)
23-23
: Great job reactivating the test!The test is now active and ready to validate the bug resolution. Make sure to keep the test focused and efficient.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10316852912. |
/ci-test-limit |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10317230880. |
There was a problem hiding this 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
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 (1)
app/client/cypress/limited-tests.txt (1)
2-2
: Good Job! The test focus is well-adjusted.The change to include
GraphQL_Binding_Bug16702_Spec.ts
in the limited tests aligns with the PR's goal to address specific issues. This helps ensure that the test suite focuses on resolving critical bugs.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10317230880. |
/ci-test-limit runId=10317230880 |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10318304444. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10318304444. |
/ci-test-limit runId=10317230880 |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10319765095. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10319765095. |
/ci-test-limit runId=10317230880 |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10346709307. |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10365574087. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10365574087. |
/ci-test-limit |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10367754008. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10367754008. |
/ci-test-limit |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10370254371. |
/ci-test-limit |
1 similar comment
/ci-test-limit |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10370269798. |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10370270847. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10370254371. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10370269798. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10370270847. |
Description
Context:
This cypress test is asserting the fixes made for bug
Bug recording: https://www.loom.com/share/ccf9fccc89064ee7b4230aaf5bf3cc52
Basically bug was that when using bindings inside query of graphQL API, autocomplete menu shows up for first binding, but not for second binding. This test case asserts that autocomplete menu shows up every time inside binding for query
EE PR: https://github.com/appsmithorg/appsmith-ee/pull/4856
This PR fixes the skipped test of spec file: cypress/e2e/Regression/ClientSide/BugTests/GraphQL_Binding_Bug16702_Spec.ts
Fixes #35147
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="@tag.Datasource"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10383572807
Commit: 0a655d7
Cypress dashboard.
Tags:
@tag.Datasource
Spec:
Wed, 14 Aug 2024 09:15:08 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit
Summary by CodeRabbit