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

Do Not merge : Running test #37235

Open
wants to merge 1 commit into
base: release
Choose a base branch
from
Open

Conversation

sagar-qa007
Copy link
Contributor

@sagar-qa007 sagar-qa007 commented Nov 5, 2024

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 #37234

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • Chores
    • Updated the test configuration to execute a new test file for limited tests.

Copy link
Contributor

coderabbitai bot commented Nov 5, 2024

Walkthrough

The pull request updates a configuration file for Cypress tests, specifically changing the test file path from Fork_Template_spec.js to EmbedSettings_spec.js. This adjustment ensures that the correct test is executed during limited test runs, while other comments in the file remain unchanged.

Changes

File Path Change Summary
app/client/cypress/limited-tests.txt Updated test file path from Fork_Template_spec.js to EmbedSettings_spec.js.

Assessment against linked issues

Objective Addressed Explanation
Verify and fix randomly failing test cases (#37234)

Possibly related PRs

Suggested labels

skip-changelog, ok-to-test, Test

Suggested reviewers

  • ApekshaBhosale

🎉 In the land of tests, a path was changed,
From Fork to Embed, the files rearranged.
Cypress now knows where to go,
Running the tests with a steady flow!
Cheers to the code, as we all unite,
For cleaner tests and a future bright! 🌟


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

@sagar-qa007
Copy link
Contributor Author

/ci-test-limit-count run_count=100

Copy link

github-actions bot commented Nov 5, 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: 0

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

Line range hint 1-6: Consider documenting the test selection criteria.

Since this file is critical for CI and used for running minimum specs, it would be helpful to document:

  1. Why this particular test was chosen for limited runs
  2. What criteria should be used when updating this file

Add a comment explaining the test selection criteria:

 # To run only limited tests - give the spec names in below format:
 cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js
+# Note: Tests listed here should be:
+# - Stable and reliable
+# - Representative of critical functionality
+# - Quick to execute
 # For running all specs - uncomment below:
 #cypress/e2e/**/**/*
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6660bd9 and 6f8cc65.

📒 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 (1)
app/client/cypress/limited-tests.txt (1)

2-2: Verify the existence of the new test file.

Let's ensure the specified test file exists and is the appropriate one for limited test runs.

✅ Verification successful

Test file exists and is correctly referenced

The specified test file EmbedSettings_spec.js exists at the correct location and follows the expected path format for Cypress tests. The file is only referenced in the limited-tests configuration, which is appropriate for its intended use.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the existence of the specified test file
fd "EmbedSettings_spec.js" app/client/cypress/e2e/Regression/ClientSide/EmbedSettings/

# Check if there are any references to this test in other configuration files
rg "EmbedSettings_spec.js" app/client/cypress/

Length of output: 321

Copy link

github-actions bot commented Nov 5, 2024

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

***** Repeat Run Summary ***** Total Tests with repeat: 100 Total Passed: 0 Total Failed: 100 Total Skipped: 0 *****************************

@sagar-qa007 sagar-qa007 reopened this Nov 12, 2024
@sagar-qa007
Copy link
Contributor Author

/ci-test-limit-count run_count=100

Copy link

Copy link

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

***** Repeat Run Summary ***** Total Tests with repeat: 100 Total Passed: 0 Total Failed: 100 Total Skipped: 0 *****************************

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 Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant