The test runner was incorrectly running all samples that start with a given prefix instead of just the exact sample that changed. For example, when nextjs-static was added in PR #417, the test runner ran tests for all samples starting with nextjs including nextjs, nextjs-blog, nextjs-claude, nextjs-cv, nextjs-documentation, and nextjs-postgres.

Root Cause

The issue was in the GitHub Actions workflow deploy-changed-samples.yml where sample names from changed_samples.txt were passed directly to the loadtest tool as regex patterns. Since the loadtest tool treats the -s parameter as regular expressions, unescaped sample names like nextjs-static would match any sample containing the substring nextjs.

Solution

Modified the workflow to:

1. Escape regex special characters in sample names using awk '{gsub(/[.*+?^${}()|[\]\\]/, "\\\\&")}'
2. Anchor patterns with ^ and $ to ensure exact matching: ^sample-name$

This ensures that when a sample like nextjs-static changes, only that exact sample is tested, not all samples with nextjs in their name.

Testing

Verified the fix works correctly:

• ✅ Before: Pattern nextjs matched 6 samples (nextjs, nextjs-blog, nextjs-claude, nextjs-cv, nextjs-documentation, nextjs-postgres)
• ✅ After: Pattern ^nextjs$ matches only 1 sample (nextjs)
• ✅ Multiple samples work correctly when multiple files change
• ✅ Intentional regex patterns still work (e.g., python.* for all python samples)

Fixes #418.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.