Prompt

How do I run end-to-end tests on every pull request?

Technology / CI/CD & DevOps1 observationLast seen Oct 19, 2026

Latest observation

Oct 19, 2026OpenAI APIWeb search: off

To run end-to-end tests on every pull request, set up CI to trigger on pull request events and execute your E2E test suite automatically.

General approach

  1. Define your E2E tests
    Use a framework like Playwright, Cypress, Selenium, or TestCafe.

  2. Create a CI workflow/pipeline
    Configure it to run when a PR is opened or updated.

  3. Install dependencies

  4. Start your app and any required services

  5. Run the E2E tests

  6. Fail the PR if tests fail

Example: GitHub Actions

If your repo is on GitHub, add a workflow like this:

name: E2E Tests

on:
  pull_request:

jobs:
  e2e:
    runs-on: ubuntu-latest

    services:
      postgres:
        image: postgres:15
        env:
          POSTGRES_PASSWORD: password
          POSTGRES_DB: app_test
        ports:
          - 5432:5432
        options: >-
          --health-cmd="pg_isready -U postgres"
          --health-interval=10s
          --health-timeout=5s
          --health-retries=5

    steps:
      - uses: actions/checkout@v4

      - name: Set up Node
        uses: actions/setup-node@v4
        with:
          node-version: 20

      - name: Install dependencies
        run: npm ci

      - name: Build app
        run: npm run build

      - name: Start app
        run: npm start &

      - name: Wait for app
        run: npx wait-on http://localhost:3000

      - name: Run E2E tests
        run: npm run test:e2e

Notes

  • Use pull_request so tests run on every PR update.
  • If your app needs a database, cache, or other service, define it in CI.
  • Make sure your test environment is isolated and reproducible.
  • Consider running tests in parallel if the suite is large.
  • Optionally add required status checks so PRs can’t be merged unless E2E passes.

If you use another CI

  • GitLab CI: use rules: if: $CI_PIPELINE_SOURCE == "merge_request_event"
  • CircleCI: use workflows triggered on pull requests
  • Azure DevOps / Jenkins: configure PR build triggers similarly

If you want, I can give you a ready-to-use config for GitHub Actions, GitLab CI, or Cypress/Playwright specifically.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.