Create a starter Gherkin BDD integration test setup with Cucumber.js

.eleventyignore

@@ -1,3 +1,4 @@
 ./README.md
 ./_image_sources
 ./_drafts
+./tests

.github/workflows/on_call_staging_test.yaml

@@ -18,6 +18,15 @@ jobs:
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
 
+      - name: Setup Node.js for BDD tests
+        uses: actions/setup-node@v4
+        with:
+          node-version: '18'
+          cache: 'npm'
+
+      - name: Install dependencies for BDD tests
+        run: npm ci
+
       - name: Prepare staging context  
         run: |
           # Copy staging files into the _site directory for the docker build
@@ -42,3 +51,23 @@ jobs:
 
           # Exit with the test result
           exit $exit_code
+
+      - name: Run BDD Tests
+        run: |
+          # Run BDD tests and capture output for summary
+          set +e  # Don't exit on error so we can capture output
+          echo "## BDD Test Results" >> $GITHUB_STEP_SUMMARY
+          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
+          npm run test:bdd 2>&1 | tee bdd_output.txt
+          bdd_exit_code=$?
+          cat bdd_output.txt >> $GITHUB_STEP_SUMMARY
+          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
+
+          if [ $bdd_exit_code -eq 0 ]; then
+            echo "✅ BDD tests passed" >> $GITHUB_STEP_SUMMARY
+          else
+            echo "⚠️ BDD tests failed (this is expected as step definitions are not yet implemented)" >> $GITHUB_STEP_SUMMARY
+          fi
+
+          # Don't fail the workflow for now since tests are expected to fail
+          exit 0

README.md

@@ -22,6 +22,24 @@ docker compose run shell
 
 **Note:** `node_modules` are managed inside the container. You do not need to run `npm install` on your host.
 
+## Running Tests
+
+This project uses BDD (Behavior-Driven Development) tests with Gherkin syntax powered by Cucumber.js.
+
+### Running Unit Tests
+
+To run the BDD tests locally:
+```bash
+npm run test:bdd
+```
+
+To run tests in Docker:
+```bash
+docker compose run test
+```
+
+The tests are located in `tests/staging/features/` and use Gherkin feature files to describe expected behavior.
+
 ## Preparing to contribute
 
 This project uses the following tools for development:

docker-compose.yml

@@ -117,3 +117,15 @@ services:
       timeout: 5s
       retries: 5
       start_period: 30s
+
+  # BDD Testing service
+  test:
+    build:
+      context: .
+      dockerfile: tests.Dockerfile
+    volumes:
+      - ./tests:/app/tests
+      - ./package.json:/app/package.json
+      - ./package-lock.json:/app/package-lock.json
+    profiles:
+      - manual