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

test: PartialExport_Widgets_spec - updated exported json file to compare and added confirmation of successful import #33090

Merged
merged 13 commits into from
May 7, 2024

Conversation

NandanAnantharamu
Copy link
Collaborator

@NandanAnantharamu NandanAnantharamu commented May 1, 2024

RCA:
Test was failing at comparison step where we export and compare

Solution:
Updated the WidgetsExportedOnly.json, now the comparison step is working as expected
Improved the assertions within importApp() reduced wait time and also removed the Toast message verification

/ok-to-test tags="@tag.Workspace,@tag.ImportExport"

Tip

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

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit

@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test labels May 1, 2024
Copy link
Contributor

coderabbitai bot commented May 1, 2024

Walkthrough

Walkthrough

The changes across several files in the Cypress test suite involve importing and utilizing message constants for error and success notifications. This standardizes the messages used in assertions and error handling, enhancing maintainability and readability. The modifications also include updates to test configurations and minor adjustments in test behavior.

Changes

Files Change Summary
.../GitImport/GitImport_spec.js
.../Widgets/Migration_Spec.js
.../support/Pages/GitSync.ts
.../support/gitSync.js
Replaced hardcoded strings with imported message constants for consistency and easier management.
.../limited-tests.txt Updated the spec names in the test configuration file.
.../constants/messages.ts Added new constants for import success and failure messages.
.../support/Pages/HomePage.ts Adjusted sleep times, added import success validation, and updated toast message validation using message constants.

Possibly related issues


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 23535e8 and f1cc3cf.
Files selected for processing (1)
  • app/client/cypress/support/Pages/HomePage.ts (3 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/client/cypress/support/Pages/HomePage.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.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

github-actions bot commented May 1, 2024

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

Out of diff range and nitpick comments (1)
app/client/cypress/limited-tests.txt (1)

Line range hint 7-7: Clarify the instruction for running a minimum number of specs.

- #ci-test-limit uses this file to run minimum of specs. Do not run entire suite with this command.
+ #ci-test-limit uses this file to run a minimum number of specs. Do not run the entire suite with this command.

This change improves the clarity of the instructions, ensuring that users understand the purpose and limitations of using the ci-test-limit command.

@@ -1,5 +1,5 @@
# To run only limited tests - give the spec names in below format:
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding "the" for grammatical correctness.

- # To run only limited tests - give spec names in below format:
+ # To run only limited tests - give the spec names in below format:

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.

Suggested change
# To run only limited tests - give the spec names in below format:
# To run only limited tests - give the spec names in below format:

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

Copy link

github-actions bot commented May 1, 2024

Copy link

github-actions bot commented May 1, 2024

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

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

Copy link

github-actions bot commented May 1, 2024

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

Copy link

github-actions bot commented May 1, 2024

Copy link

github-actions bot commented May 1, 2024

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

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

9 similar comments
@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

@NandanAnantharamu
Copy link
Collaborator Author

/ci-test-limit runId=8906254185

Copy link

github-actions bot commented May 2, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu
Copy link
Collaborator Author

/ok-to-test tags="@tag.Workspace @tag.ImportExport"

Copy link

github-actions bot commented May 2, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu NandanAnantharamu added ok-to-test Required label for CI and removed ok-to-test Required label for CI labels May 3, 2024
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

"Unable to import application in workspace",
"not.exist",
);
assertHelper.AssertContains(createMessage(UNABLE_TO_IMPORT_APP), "not.exist");
Copy link
Contributor

Choose a reason for hiding this comment

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

Tip

Codebase Verification

The usage of createMessage(UNABLE_TO_IMPORT_APP) is found only at one location in the codebase (./app/client/cypress/support/gitSync.js:237). This might indicate that the message is either very specific to a particular scenario or underutilized. It would be beneficial to review whether this limited usage aligns with the intended enhancements of messaging consistency.

  • ./app/client/cypress/support/gitSync.js:237
Analysis chain

Usage of createMessage(UNABLE_TO_IMPORT_APP) aligns with PR objectives to enhance messaging consistency.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the new message is integrated correctly across the test suite.

# Test: Search for the usage of `createMessage(UNABLE_TO_IMPORT_APP)` to ensure it's used consistently. Expect: Matches.
ast-grep --lang javascript --pattern $'createMessage(UNABLE_TO_IMPORT_APP)'

Length of output: 201

@NandanAnantharamu
Copy link
Collaborator Author

/ok-to-test tags="@tag.Workspace @tag.ImportExport"

@NandanAnantharamu NandanAnantharamu removed the ok-to-test Required label for CI label May 3, 2024
Copy link

github-actions bot commented May 3, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu NandanAnantharamu added the ok-to-test Required label for CI label May 3, 2024
@NandanAnantharamu
Copy link
Collaborator Author

/ok-to-test tags="@tag.Workspace,@tag.ImportExport"

Copy link

github-actions bot commented May 3, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu NandanAnantharamu added ok-to-test Required label for CI and removed ok-to-test Required label for CI labels May 3, 2024
@NandanAnantharamu
Copy link
Collaborator Author

/ok-to-test tags="@tag.Workspace,@tag.ImportExport"

Copy link

github-actions bot commented May 3, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu
Copy link
Collaborator Author

/ok-to-test tags="@tag.Workspace,@tag.ImportExport"

@NandanAnantharamu NandanAnantharamu removed the ok-to-test Required label for CI label May 3, 2024
Copy link

github-actions bot commented May 3, 2024

Whoops! Looks like you're using an outdated method of running the Cypress suite.
Please check this doc to learn how to correct this!

@NandanAnantharamu NandanAnantharamu added the ok-to-test Required label for CI label May 3, 2024
@trishaanand trishaanand merged commit 87d535a into release May 7, 2024
12 of 13 checks passed
@trishaanand trishaanand deleted the test/fixPartiallyImport branch May 7, 2024 05:53
trishaanand added a commit that referenced this pull request May 8, 2024
… to compare and added confirmation of successful import" (#33254)

Reverts #33090
@NandanAnantharamu NandanAnantharamu restored the test/fixPartiallyImport branch May 8, 2024 05:25
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 Test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants