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: fix Onboarding/CreateNewApp flaky test #21347

Merged
merged 7 commits into from
Mar 15, 2023

Conversation

akash-codemonk
Copy link
Contributor

@akash-codemonk akash-codemonk commented Mar 13, 2023

Description

Test cleanup to remove commands which are not part of the user flow. Have ran the test suite 3 times and it has passed all the time. Not sure about why the 503 happens sometimes

Fixes #21327

Type of change

  • Chore (housekeeping or task changes that don't impact user perception)

Checklist:

Dev activity

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • PR is being merged under a feature flag

@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Mar 13, 2023
@akash-codemonk
Copy link
Contributor Author

/ok-to-test

@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4401296678.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4401296678_1

@akash-codemonk
Copy link
Contributor Author

/ok-to-test

@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4401820992.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4401820992_1

@akash-codemonk
Copy link
Contributor Author

/ok-to-test

@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4403954534.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4403954534_1

@github-actions
Copy link

The following are new failures, please fix them before merging the PR
  1. cypress/integration/Regression_TestSuite/Application/CommunityIssues_Spec.ts
  2. cypress/integration/Regression_TestSuite/ClientSideTests/VisualTests/DatasourcePageLayout_spec.js
  3. cypress/integration/Regression_TestSuite/ClientSideTests/VisualTests/JSEditorIndent_spec.js

@akash-codemonk
Copy link
Contributor Author

/ok-to-test

@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4404919810.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4404919810_1

@akash-codemonk
Copy link
Contributor Author

/ok-to-test

@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4414258959.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4414258959_1

_.homePage.CreateNewWorkspace(workspaceName);
_.homePage.CreateAppInWorkspace(workspaceName); //Since welcome tour always creates app in 1st workspace available
_.homePage.NavigateToHome();
});
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We aren't really using the workspaceName variable anywhere in the test so have removed this . Removing this also seems to have stopped the 503 errors not sure why though

Copy link
Contributor

Choose a reason for hiding this comment

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

No, this does not solve the issue. I add the new workspace creation code as a part of script fix - for 503. Tried adding new workspace, creating new application in it & then try to click on welcome tour. This will not/does not solve the 503.

.click()
.wait(4000);
}
});
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The CloseReconnectDataSourceModal and clicking on the welcomeTour are repeated which are not required to run the test, so have removed them.

Copy link
Contributor

Choose a reason for hiding this comment

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

This was added since we see the Reconnect modal dialog appearing out of nowhere in this test flow & test failing to click on welcome tour. Removing this also will not solve the 503 issue.

Copy link
Contributor Author

@akash-codemonk akash-codemonk Mar 15, 2023

Choose a reason for hiding this comment

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

If the reconnect modal does appear then either it is a bug or some issue the fork api on ci. Either ways keeping this is a workaround. I can have a look at it when it happens next time, so far the 4 times we ran it does not seem to have happened.
Yes I don't think it fixes the 503 issue.

@github-actions github-actions bot added Bug Something isn't working CI impacted Issues that cause CI failures and need to be addressed on priority by respective pods Needs Triaging Needs attention from maintainers to triage IDE Pod Issues that new developers face while exploring the IDE Release Welcome Screen Issues related to the welcome screen and removed Bug Something isn't working labels Mar 14, 2023
@akash-codemonk akash-codemonk requested review from Vijetha-Kaja and Aishwarya-U-R and removed request for Vijetha-Kaja March 14, 2023 11:14
@Aishwarya-U-R
Copy link
Contributor

/ok-to-test sha=9abd3d2

@github-actions github-actions bot added the Bug Something isn't working label Mar 14, 2023
@github-actions
Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4419574598.
Workflow: Appsmith External Integration Test Workflow.
Commit: 9abd3d2.
PR: 21347.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21347&runId=4419574598_1

@Aishwarya-U-R Aishwarya-U-R added the Test Plan Approved Manual/Cypress tests covers changes made on the PR. Else, add skip-testPlan label if not applicable label Mar 15, 2023
@Aishwarya-U-R Aishwarya-U-R merged commit 4799d0b into release Mar 15, 2023
@Aishwarya-U-R Aishwarya-U-R deleted the chore/onboarding-test branch March 15, 2023 02:20
@Nikhil-Nandagopal Nikhil-Nandagopal added Onboarding Product Issues related to onboarding new developers and removed IDE Pod Issues that new developers face while exploring the IDE labels Aug 6, 2024
Copy link
Contributor

coderabbitai bot commented Aug 6, 2024

Warning

Rate limit exceeded

@Nikhil-Nandagopal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 25 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between f2e1df7 and 9abd3d2.


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

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working CI impacted Issues that cause CI failures and need to be addressed on priority by respective pods Needs Triaging Needs attention from maintainers to triage Onboarding Product Issues related to onboarding new developers Release skip-changelog Adding this label to a PR prevents it from being listed in the changelog Test Plan Approved Manual/Cypress tests covers changes made on the PR. Else, add skip-testPlan label if not applicable Welcome Screen Issues related to the welcome screen
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: CI failure: Page randomly throws 503 on clicking welcome tour
3 participants