Skip to content

Added E2E Test cases#333

Merged
chetanbothra merged 39 commits intostagingfrom
e2e
Jun 20, 2025
Merged

Added E2E Test cases#333
chetanbothra merged 39 commits intostagingfrom
e2e

Conversation

@chetanbothra
Copy link
Contributor

@chetanbothra chetanbothra commented Jun 13, 2025

Test Case run

  1. Every day at midnight
  2. After commit is merged to staging

Testing and approved by Naveen PRO-3226

Summary by CodeRabbit

  • Chores
    • Introduced automated end-to-end UI testing in the CI pipeline, running tests on the staging branch and generating detailed reports.
    • Test results are summarized and sent to a Slack channel, including links to relevant reports and information on any test failures.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 13, 2025

Walkthrough

A new CircleCI configuration file is added to automate end-to-end UI testing using Cypress and Playwright. The pipeline installs dependencies, runs tests, generates reports, and posts a summary to Slack. The workflow is configured to trigger only on the staging branch.

Changes

File(s) Change Summary
.circleci/config.yml Added CircleCI configuration for E2E UI testing with Cypress/Playwright, reporting, and Slack integration.

Sequence Diagram(s)

sequenceDiagram
    participant CircleCI
    participant GitHub
    participant E2E Repo
    participant Slack

    GitHub->>CircleCI: Push to staging branch
    CircleCI->>E2E Repo: Clone E2E test repository
    CircleCI->>CircleCI: Install dependencies & Playwright browsers
    CircleCI->>CircleCI: Replace environment variables
    CircleCI->>CircleCI: Run Cypress/Playwright tests
    CircleCI->>CircleCI: Generate Mochawesome report
    CircleCI->>CircleCI: Parse report, format Slack message
    CircleCI->>Slack: Send test summary to Slack channel
Loading

Poem

In the warren, the tests now run,
With Cypress and Playwright, oh what fun!
Reports are gathered, Slack gets the news,
On staging branch, we chase no blues.
Rabbits rejoice, the pipeline’s begun—
End-to-end journeys, all in one!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

@cloudflare-workers-and-pages
Copy link

Deploying x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 59c83b4
Status: ✅  Deploy successful!
Preview URL: https://c348c4b6.x-e62.pages.dev
Branch Preview URL: https://e2e.x-e62.pages.dev

View logs

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

🔭 Outside diff range comments (1)
.circleci/config.yml (1)

111-121: 🛠️ Refactor suggestion

Workflow filters do not meet PR objectives
The pr_triggered_e2e_tests workflow only runs on staging, but per PR objectives it should also run on develop after merges and nightly at midnight. Proposed adjustment:

 workflows:
   version: 2
   pr_triggered_e2e_tests:
-    jobs:
-      - e2e-tests:
-          filters:
-            branches:
-              only:
-                - staging
+    triggers:
+      - schedule:
+          cron: "0 0 * * *"
+          filters:
+            branches:
+              only: [develop]
+    jobs:
+      - e2e-tests:
+          filters:
+            branches:
+              only: [staging, develop]
🧹 Nitpick comments (3)
.circleci/config.yml (3)

3-5: Unused Slack orb
The slack: circleci/slack@3.4.2 orb is declared but never utilized. Remove it or replace the custom curl step with the orb’s slack/notify command for consistency.


39-41: Restrict file permissions on test report
Using chmod 777 is overly permissive. Limit write access to the owner:

-            chmod 777 -R /tmp/mochawesome-report
+            chmod 755 -R /tmp/mochawesome-report

27-27: Remove trailing whitespace
YAMLlint flags trailing spaces on these lines. Please trim the trailing spaces to satisfy lint rules.

Also applies to: 106-106

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 27-27: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a4151c7 and 59c83b4.

📒 Files selected for processing (1)
  • .circleci/config.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.circleci/config.yml

[error] 27-27: trailing spaces

(trailing-spaces)


[error] 106-106: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build

@chetanbothra chetanbothra requested review from IAmKio and RanaBug June 16, 2025 04:18
Copy link
Collaborator

@IAmKio IAmKio left a comment

Choose a reason for hiding this comment

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

LGTM but @sankhavaramsaitulasiram could you review this please also?

@chetanbothra chetanbothra merged commit 64fa25e into staging Jun 20, 2025
7 checks passed
@chetanbothra chetanbothra deleted the e2e branch June 20, 2025 08:37
@coderabbitai coderabbitai bot mentioned this pull request Nov 25, 2025
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants