Skip to content

Conversation

@Divyoth1234
Copy link

@Divyoth1234 Divyoth1234 commented Dec 5, 2025

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior?

EverShop currently does not run testRigor-based end-to-end tests in CI. There is no automated E2E coverage via testRigor wired into repository workflows.

Issue Number: N/A

What is the new behavior?

This PR adds testRigor end-to-end testing integration:

  • EverShop is started in CI using the official Docker Compose setup.
  • Demo data is seeded and an admin user is created in CI.
  • testRigor CLI triggers the EverShop suite on testRigor and runs against http://localhost:3000/admin.
  • Test cases and reusable rules are loaded directly from this repo.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Changes proposed in this Pull Request:

This pull request adds end-to-end test cases using testRigor for EverShop.

testRigor is an AI-powered end-to-end testing platform that allows you to write tests in plain English. This setup enables automated testing of EverShop’s UI and functionality from a user’s perspective, covering Admin and Storefront flows.

What’s included:

  • 1 new workflow file that performs a full run of this test suite when triggered.
  • 1 new folder at packages/evershop/src/Tests/e2e-testcases/ containing:
    • testcases/ (plain-English tests)
    • reusable-rules/ (shared rules)
    • README.md

Latest successful CI run:
https://github.com/Divyoth1234/evershop/actions/runs/19954170798

Why testRigor?

  • Test cases written in plain English: anyone can contribute automated tests without coding, enabling broader coverage.
  • Reduced maintenance overhead: tests are resilient to UI changes.
  • Cross-platform coverage: works across desktop, mobile, and web.

How to test the changes in this Pull Request:

CI (automatic)

  • Any push or pull request triggers .github/workflows/evershop-testrigor.yml.
  • The workflow starts EverShop via Docker Compose, seeds demo data, creates an admin user, then runs the testRigor suite against http://localhost:3000/admin.

Local (manual)

1. Start EverShop locally:
   ```bash
   curl -sSL https://raw.githubusercontent.com/evershopcommerce/evershop/main/docker-compose.yml > docker-compose.yml
   docker compose up -d

2.Seed demo data and create an admin user:
    APP_CONTAINER=$(docker ps --format '{{.Names}}' | grep evershop-app | head -n 1)

    docker exec "$APP_CONTAINER" npm run seed -- --all
    docker exec "$APP_CONTAINER" npm run user:create -- \
      --email "<ADMIN_EMAIL>" \
      --password "<ADMIN_PASSWORD>" \
      --name "Admin"

3. Install testRigor CLI:
    npm install -g testrigor-cli

4. Run the suite:

    testrigor test-suite run <SUITE_ID> \
      --token <CI_TOKEN> \
      --localhost \
      --test-cases-path packages/evershop/src/Tests/e2e-testcases/testcases/**/*.txt \
      --rules-path packages/evershop/src/Tests/e2e-testcases/reusable-rules/**/*.txt \
      --url "http://localhost:3000/admin"

Replace the items between "< >" with the corresponding values:

  • SUITE_ID: the ID of the test suite itself, it's located in the URL (i.e. for the following test suite: https://app.testrigor.com/test-suites/oJvBxgjY5A8Pw48hj/test-cases , the SUITE_ID is: oJvBxgjY5A8Pw48hj

  • CI_TOKEN: To get the CI token follow these steps:

    • Open the test suite that has been previously set up.
    • Click "CI/CD Integration" located on the sidebar.
    • The auth token should be located there (refer to the image posted below).
    • Copy the CI token then use it on the CLI command.
Screenshot 2025-12-04 at 4 29 04 PM

@Divyoth1234 Divyoth1234 changed the title Add testrigor e2e folder Added e2e test cases using testRigor Dec 5, 2025
@Divyoth1234 Divyoth1234 force-pushed the add-testrigor-e2e-folder branch from 90056b3 to 76972f7 Compare December 5, 2025 10:34
@Divyoth1234 Divyoth1234 marked this pull request as ready for review December 11, 2025 09:37
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.

1 participant