Split root Pipfile per test suite for true CI path-filter isolation

.github/workflows/desktop_web.yml

@@ -6,18 +6,12 @@ on:
         - main
     paths:
       - 'best_practice/desktop_web/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/desktop_web.yml'
   pull_request:
     branches:
         - main
     paths:
       - 'best_practice/desktop_web/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/desktop_web.yml'
   schedule:
     - cron: "0 9 * * *"
@@ -26,7 +20,10 @@ jobs:
   python-tests:
     name: Tests
     runs-on: ubuntu-latest
-
+    defaults:
+      run:
+        working-directory: best_practice/desktop_web
+
     steps:
       - uses: actions/checkout@v7
       - name: Setup Python

.github/workflows/mobile_native.yml

@@ -6,18 +6,12 @@ on:
         - main
     paths:
       - 'best_practice/mobile_native/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/mobile_native.yml'
   pull_request:
     branches:
         - main
     paths:
       - 'best_practice/mobile_native/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/mobile_native.yml'
   schedule:
     - cron: "0 9 * * *"
@@ -26,6 +20,9 @@ jobs:
   python-tests:
     name: Tests
     runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: best_practice/mobile_native
     strategy:
       fail-fast: false
       matrix:

.github/workflows/mobile_web.yml

@@ -6,18 +6,12 @@ on:
         - main
     paths:
       - 'best_practice/mobile_web/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/mobile_web.yml'
   pull_request:
     branches:
         - main
     paths:
       - 'best_practice/mobile_web/**'
-      - 'best_practice/conftest.py'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/mobile_web.yml'
   schedule:
     - cron: "0 9 * * *"
@@ -26,6 +20,9 @@ jobs:
   python-tests:
     name: Tests
     runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: best_practice/mobile_web
     strategy:
       fail-fast: false
       matrix:

.github/workflows/robot_desktop_web.yml

@@ -6,16 +6,12 @@ on:
         - main
     paths:
       - 'examples/robotframework/desktop_web/**'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/robot_desktop_web.yml'
   pull_request:
     branches:
         - main
     paths:
       - 'examples/robotframework/desktop_web/**'
-      - 'Pipfile'
-      - 'Pipfile.lock'
       - '.github/workflows/robot_desktop_web.yml'
   schedule:
     - cron: "0 9 * * *"
@@ -24,7 +20,10 @@ jobs:
   python-tests:
     name: Tests
     runs-on: ubuntu-latest
-
+    defaults:
+      run:
+        working-directory: examples/robotframework/desktop_web
+
     steps:
       - uses: actions/checkout@v7
       - name: Setup Python

.github/workflows/python.yml → .github/workflows/selenium_demo.yml

@@ -1,37 +1,29 @@
-name: Demo Python Tests
+name: Selenium Demo Tests
 
 on:
   push:
     branches:
         - main
     paths:
-      - 'best_practice/desktop_web/**'
-      - 'best_practice/conftest.py'
       - 'examples/selenium/**'
-      - 'Pipfile'
-      - 'Pipfile.lock'
-      - '.github/workflows/python.yml'
+      - '.github/workflows/selenium_demo.yml'
   pull_request:
     branches:
         - main
     paths:
-      - 'best_practice/desktop_web/**'
-      - 'best_practice/conftest.py'
       - 'examples/selenium/**'
-      - 'Pipfile'
-      - 'Pipfile.lock'
-      - '.github/workflows/python.yml'
+      - '.github/workflows/selenium_demo.yml'
   schedule:
     - cron: "0 9 * * *"
 
 jobs:
   python-tests:
     name: Tests
     runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        test: [ best-practice-desktop-us, demo]
+    defaults:
+      run:
+        working-directory: examples/selenium
+
     steps:
       - uses: actions/checkout@v7
       - name: Setup Python
@@ -42,8 +34,8 @@ jobs:
         uses: dschep/install-pipenv-action@v1
       - name: Install dependencies
         run: pipenv install
-      - name: Run ${{ matrix.test }} tests
+      - name: Run demo tests
         env:
           SAUCE_USERNAME: ${{ secrets.SAUCE_USERNAME }}
           SAUCE_ACCESS_KEY: ${{ secrets.SAUCE_ACCESS_KEY }}
-        run: pipenv run ${{ matrix.test }}
+        run: pipenv run demo

README.md

@@ -48,38 +48,45 @@ and these cover using
 - Mobile Web browsers on Sauce emulators/simulators, and
 - Real devices to test native mobile apps.
 
-These samples are executed using Pipenv for simplicity. You can find a list of 
-available executions in the `Pipfile` under the `[scripts]` section. These 
-executions demonstrate how to run tests in parallel on the Sauce Labs.
+These samples are executed using Pipenv for simplicity. Each test suite has its
+own `Pipfile` in its own directory, so dependencies and CI triggers stay scoped
+to just that suite instead of one shared repo-wide dependency file. To run a
+suite: `cd` into its directory, run `pipenv install`, then `pipenv run
+<script-name>`.
 
 ## Available Pipenv scripts
 
-Below are the scripts defined in `Pipfile` grouped by purpose. Run any of them
-with `pipenv run <script-name>`.
+Below are the scripts defined in each suite's own `Pipfile`, grouped by
+directory. `cd` into the listed directory first, then run
+`pipenv run <script-name>`.
 
-- Best-practice (desktop)
+- `best_practice/desktop_web/`
   - `best-practice-desktop-us` — runs desktop best-practice tests against the US data center
   - `best-practice-desktop-eu` — runs desktop best-practice tests against the EU data center
 
-- Best-practice (mobile web)
+- `best_practice/mobile_web/`
   - `best-practice-mobile-web-vdc-us` — runs mobile web tests on virtual devices (VDC) in US
   - `best-practice-mobile-web-vdc-eu` — runs mobile web tests on virtual devices (VDC) in EU
   - `best-practice-mobile-web-rdc-us` — runs mobile web tests on real devices (RDC) in US
   - `best-practice-mobile-web-rdc-eu` — runs mobile web tests on real devices (RDC) in EU
 
-- Best-practice (mobile native)
+- `best_practice/mobile_native/`
   - `best-practice-mobile-native-us-android` — runs native Android tests in US
   - `best-practice-mobile-native-eu-android` — runs native Android tests in EU
   - `best-practice-mobile-native-us-ios` — runs native iOS tests in US
   - `best-practice-mobile-native-eu-ios` — runs native iOS tests in EU
 
-- Examples & demos
+- `examples/selenium/`
   - `demo` — runs the Selenium examples
+
+- `examples/playwright/`
   - `playwright-tests` — runs the Playwright examples
 
-- Robotframework multi-run scripts (Pabot)
+- `examples/robotframework/desktop_web/`
   - `robot-desktop-web-us` — runs desktop web robot tests against US datacenter
   - `robot-desktop-web-eu` — runs desktop web robot tests against EU datacenter
+
+- `examples/robotframework/native_mobile/`
   - `robot-android-us` — runs native Android robot tests against US datacenter
   - `robot-android-eu` — runs native Android robot tests against EU datacenter
   - `robot-ios-us` — runs native iOS robot tests against US datacenter