Skip to content

Add tests for auto-injected VQS header injection#1099

Merged
pranaygp merged 1 commit into
mainfrom
pg/add-vqs-header-injection-tests
Feb 20, 2026
Merged

Add tests for auto-injected VQS header injection#1099
pranaygp merged 1 commit into
mainfrom
pg/add-vqs-header-injection-tests

Conversation

@pranaygp
Copy link
Copy Markdown
Contributor

Summary

  • Follow-up to Auto-inject workflow run/step ID VQS headers from queue payload #1098 — adds unit tests for getHeadersFromPayload in @workflow/world-vercel
  • Tests the queue() path: workflow payloads get x-workflow-run-id, step payloads get both x-workflow-run-id and x-workflow-step-id, health checks get no workflow headers
  • Tests caller header override precedence
  • Tests the createQueueHandler delayed re-enqueue path inherits headers for both workflow and step payloads

Test plan

  • pnpm vitest run src/queue.test.ts — 17/17 passing

🤖 Generated with Claude Code

Tests cover:
- Workflow payload -> x-workflow-run-id header
- Step payload -> x-workflow-run-id + x-workflow-step-id headers
- Health check payload -> no workflow headers
- Caller headers override auto-injected headers
- Delayed re-enqueue inherits headers for both payload types

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pranaygp pranaygp requested review from Copilot and ctgowrie February 17, 2026 21:51
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 17, 2026

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 17, 2026

⚠️ No Changeset found

Latest commit: d4ec0b3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 17, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
❌ ▲ Vercel Production 533 1 38 572
✅ 💻 Local Development 556 0 68 624
✅ 📦 Local Production 556 0 68 624
✅ 🐘 Local Postgres 556 0 68 624
✅ 🪟 Windows 49 0 3 52
❌ 🌍 Community Worlds 110 46 9 165
✅ 📋 Other 135 0 21 156
Total 2495 47 275 2817

❌ Failed Tests

▲ Vercel Production (1 failed)

nextjs-turbopack (1 failed):

  • error handling retry behavior workflow completes despite transient 5xx on step_completed
🌍 Community Worlds (46 failed)

mongodb (1 failed):

  • webhookWorkflow

turso (45 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • parallelSleepWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling retry behavior workflow completes despite transient 5xx on step_completed
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • cancelRun - cancelling a running workflow
  • cancelRun via CLI - cancelling a running workflow
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

❌ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 48 0 4
✅ example 48 0 4
✅ express 48 0 4
✅ fastify 48 0 4
✅ hono 48 0 4
❌ nextjs-turbopack 50 1 1
✅ nextjs-webpack 51 0 1
✅ nitro 48 0 4
✅ nuxt 48 0 4
✅ sveltekit 48 0 4
✅ vite 48 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
✅ vite-stable 45 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
✅ vite-stable 45 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
✅ vite-stable 45 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 49 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 48 1 3
✅ redis-dev 3 0 0
✅ redis 49 0 3
✅ turso-dev 3 0 0
❌ turso 4 45 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 45 0 7
✅ e2e-local-postgres-nest-stable 45 0 7
✅ e2e-local-prod-nest-stable 45 0 7

📋 View full workflow run


Some E2E test jobs failed:

  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 17, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.031s (+15.4% 🔺) 1.005s (~) 0.973s 10 1.00x
💻 Local Express 0.032s (+21.6% 🔺) 1.005s (~) 0.973s 10 1.02x
💻 Local Next.js (Turbopack) 0.040s 1.005s 0.965s 10 1.28x
🌐 Redis Next.js (Turbopack) 0.047s 1.005s 0.958s 10 1.48x
🌐 MongoDB Next.js (Turbopack) 0.100s 1.008s 0.908s 10 3.18x
🐘 Postgres Nitro 0.131s (+20.4% 🔺) 1.010s (~) 0.879s 10 4.18x
🐘 Postgres Next.js (Turbopack) 0.484s 1.010s 0.525s 10 15.43x
🐘 Postgres Express 0.498s (+253.2% 🔺) 1.010s (~) 0.512s 10 15.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 0.610s (-25.3% 🟢) 2.044s (-4.8%) 1.434s 10 1.00x
▲ Vercel Nitro 0.999s (+38.6% 🔺) 2.370s (-15.4% 🟢) 1.371s 10 1.64x
▲ Vercel Express 1.076s (+49.0% 🔺) 2.226s (~) 1.150s 10 1.76x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.097s 2.005s 0.908s 10 1.00x
💻 Local Nitro 1.103s (+2.6%) 2.006s (~) 0.903s 10 1.00x
💻 Local Express 1.107s (+3.2%) 2.006s (~) 0.899s 10 1.01x
🌐 Redis Next.js (Turbopack) 1.108s 2.006s 0.898s 10 1.01x
🌐 MongoDB Next.js (Turbopack) 1.300s 2.008s 0.709s 10 1.18x
🐘 Postgres Express 2.234s (-8.1% 🟢) 2.713s (-10.1% 🟢) 0.479s 10 2.04x
🐘 Postgres Nitro 2.365s (-4.8%) 3.014s (~) 0.649s 10 2.16x
🐘 Postgres Next.js (Turbopack) 2.369s 3.013s 0.644s 10 2.16x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.427s (+41.9% 🔺) 4.351s (+21.6% 🔺) 0.924s 10 1.00x
▲ Vercel Nitro 3.494s (+50.4% 🔺) 4.616s (+37.5% 🔺) 1.122s 10 1.02x
▲ Vercel Next.js (Turbopack) 3.539s (+43.1% 🔺) 4.571s (+21.2% 🔺) 1.032s 10 1.03x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 10.705s 11.022s 0.317s 3 1.00x
💻 Local Next.js (Turbopack) 10.711s 11.022s 0.311s 3 1.00x
💻 Local Nitro 10.801s (+2.3%) 11.022s (~) 0.221s 3 1.01x
💻 Local Express 10.840s (+2.9%) 11.022s (~) 0.182s 3 1.01x
🌐 MongoDB Next.js (Turbopack) 12.290s 13.020s 0.730s 3 1.15x
🐘 Postgres Express 15.314s (-24.7% 🟢) 16.045s (-23.8% 🟢) 0.731s 2 1.43x
🐘 Postgres Next.js (Turbopack) 15.520s 16.045s 0.525s 2 1.45x
🐘 Postgres Nitro 20.394s (~) 21.056s (~) 0.662s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 18.274s (-1.2%) 19.666s (-2.3%) 1.391s 2 1.00x
▲ Vercel Nitro 18.303s (-2.5%) 19.511s (-1.7%) 1.208s 2 1.00x
▲ Vercel Express 18.442s (+3.2%) 19.268s (-0.9%) 0.826s 2 1.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.897s 27.050s 0.153s 3 1.00x
💻 Local Next.js (Turbopack) 27.192s 28.049s 0.857s 3 1.01x
💻 Local Nitro 27.442s (+2.5%) 28.050s (+3.7%) 0.608s 3 1.02x
💻 Local Express 27.527s (+3.0%) 28.052s (+3.7%) 0.525s 3 1.02x
🌐 MongoDB Next.js (Turbopack) 30.514s 31.043s 0.530s 2 1.13x
🐘 Postgres Express 37.654s (-25.2% 🟢) 38.093s (-25.5% 🟢) 0.439s 2 1.40x
🐘 Postgres Next.js (Turbopack) 37.855s 38.089s 0.234s 2 1.41x
🐘 Postgres Nitro 50.211s (~) 51.124s (~) 0.913s 2 1.87x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 44.627s (+1.4%) 45.705s (+0.5%) 1.078s 2 1.00x
▲ Vercel Nitro 45.467s (+2.1%) 46.330s (+2.1%) 0.864s 2 1.02x
▲ Vercel Next.js (Turbopack) 48.309s (+7.1% 🔺) 49.955s (+7.5% 🔺) 1.646s 2 1.08x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.428s 55.096s 0.668s 2 1.00x
💻 Local Next.js (Turbopack) 56.681s 57.099s 0.418s 2 1.04x
💻 Local Nitro 57.181s (+2.7%) 58.101s (+3.6%) 0.920s 2 1.05x
💻 Local Express 57.446s (+3.3%) 58.102s (+3.6%) 0.656s 2 1.06x
🌐 MongoDB Next.js (Turbopack) 60.996s 61.077s 0.081s 2 1.12x
🐘 Postgres Next.js (Turbopack) 74.989s 75.656s 0.668s 2 1.38x
🐘 Postgres Express 75.344s (-24.8% 🟢) 76.179s (-24.0% 🟢) 0.834s 2 1.38x
🐘 Postgres Nitro 100.426s (+8.8% 🔺) 101.224s (+8.6% 🔺) 0.798s 1 1.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 225.560s (+148.6% 🔺) 226.037s (+146.4% 🔺) 0.477s 1 1.00x
▲ Vercel Next.js (Turbopack) 231.515s (+146.8% 🔺) 232.815s (+144.2% 🔺) 1.300s 1 1.03x
▲ Vercel Nitro 241.859s (+150.3% 🔺) 243.625s (+150.5% 🔺) 1.766s 1 1.07x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.250s 2.006s 0.756s 15 1.00x
💻 Local Nitro 1.410s (+4.9%) 2.005s (~) 0.595s 15 1.13x
💻 Local Express 1.424s (+4.6%) 2.005s (~) 0.581s 15 1.14x
💻 Local Next.js (Turbopack) 1.429s 2.006s 0.576s 15 1.14x
🐘 Postgres Express 1.943s (-11.6% 🟢) 2.226s (-26.2% 🟢) 0.283s 14 1.55x
🌐 MongoDB Next.js (Turbopack) 2.123s 3.008s 0.885s 10 1.70x
🐘 Postgres Next.js (Turbopack) 2.225s 2.832s 0.606s 11 1.78x
🐘 Postgres Nitro 2.467s (+16.3% 🔺) 3.013s (+16.1% 🔺) 0.546s 10 1.97x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.478s (-2.8%) 3.414s (-2.1%) 0.936s 9 1.00x
▲ Vercel Express 2.561s (-12.7% 🟢) 3.403s (-11.0% 🟢) 0.842s 9 1.03x
▲ Vercel Next.js (Turbopack) 2.769s (+0.9%) 3.954s (+7.8% 🔺) 1.185s 8 1.12x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.494s 3.008s 0.514s 10 1.00x
💻 Local Next.js (Turbopack) 2.519s 3.008s 0.489s 10 1.01x
💻 Local Nitro 2.585s (+13.3% 🔺) 3.007s (~) 0.422s 10 1.04x
💻 Local Express 2.663s (+17.6% 🔺) 3.007s (~) 0.344s 10 1.07x
🌐 MongoDB Next.js (Turbopack) 4.825s 5.345s 0.520s 6 1.93x
🐘 Postgres Express 7.432s (-10.9% 🟢) 8.026s (-11.2% 🟢) 0.594s 4 2.98x
🐘 Postgres Nitro 8.578s (-9.9% 🟢) 9.279s (-5.1% 🟢) 0.700s 4 3.44x
🐘 Postgres Next.js (Turbopack) 12.830s 13.366s 0.536s 3 5.14x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.100s (-8.6% 🟢) 4.075s (-10.2% 🟢) 0.975s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.107s (+8.3% 🔺) 4.009s (+5.8% 🔺) 0.902s 8 1.00x
▲ Vercel Nitro 3.486s (-3.3%) 4.674s (-3.3%) 1.189s 7 1.12x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.121s 4.867s 0.746s 7 1.00x
💻 Local Nitro 7.542s (+25.5% 🔺) 8.019s (+21.2% 🔺) 0.478s 4 1.83x
💻 Local Next.js (Turbopack) 7.553s 8.266s 0.712s 4 1.83x
💻 Local Express 7.626s (+22.8% 🔺) 8.018s (+14.3% 🔺) 0.392s 4 1.85x
🌐 MongoDB Next.js (Turbopack) 9.815s 10.348s 0.533s 3 2.38x
🐘 Postgres Nitro 47.174s (-7.4% 🟢) 48.108s (-5.9% 🟢) 0.934s 1 11.45x
🐘 Postgres Express 48.222s (+1.7%) 49.118s (+2.0%) 0.896s 1 11.70x
🐘 Postgres Next.js (Turbopack) 54.346s 55.117s 0.771s 1 13.19x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 4.301s (-30.2% 🟢) 5.279s (-27.0% 🟢) 0.978s 7 1.00x
▲ Vercel Express 4.587s (-0.9%) 5.917s (+5.4% 🔺) 1.330s 6 1.07x
▲ Vercel Next.js (Turbopack) 4.915s (-31.9% 🟢) 6.429s (-26.0% 🟢) 1.514s 5 1.14x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.240s 2.006s 0.766s 15 1.00x
💻 Local Express 1.409s (+2.9%) 2.004s (~) 0.596s 15 1.14x
💻 Local Nitro 1.423s (+3.7%) 2.005s (~) 0.582s 15 1.15x
💻 Local Next.js (Turbopack) 1.452s 2.004s 0.552s 15 1.17x
🐘 Postgres Express 1.902s (-14.7% 🟢) 2.225s (-17.0% 🟢) 0.323s 14 1.53x
🌐 MongoDB Next.js (Turbopack) 2.136s 3.008s 0.871s 10 1.72x
🐘 Postgres Next.js (Turbopack) 2.166s 3.013s 0.847s 10 1.75x
🐘 Postgres Nitro 2.252s (+12.8% 🔺) 2.512s (-11.3% 🟢) 0.260s 12 1.82x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.419s (-5.1% 🟢) 3.259s (-9.0% 🟢) 0.841s 10 1.00x
▲ Vercel Express 2.544s (-2.5%) 3.198s (-11.2% 🟢) 0.654s 10 1.05x
▲ Vercel Nitro 2.754s (+16.2% 🔺) 3.862s (+15.1% 🔺) 1.108s 8 1.14x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.494s 3.008s 0.513s 10 1.00x
💻 Local Next.js (Turbopack) 2.635s 3.008s 0.373s 10 1.06x
💻 Local Nitro 2.654s (+13.1% 🔺) 3.007s (~) 0.353s 10 1.06x
💻 Local Express 2.700s (+13.2% 🔺) 3.007s (~) 0.308s 10 1.08x
🌐 MongoDB Next.js (Turbopack) 4.709s 5.175s 0.466s 6 1.89x
🐘 Postgres Express 9.099s (-17.5% 🟢) 9.530s (-16.2% 🟢) 0.431s 4 3.65x
🐘 Postgres Nitro 10.603s (-5.2% 🟢) 11.368s (-2.8%) 0.765s 3 4.25x
🐘 Postgres Next.js (Turbopack) 13.208s 13.697s 0.490s 3 5.30x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.703s (-5.4% 🟢) 3.868s (~) 1.166s 9 1.00x
▲ Vercel Next.js (Turbopack) 2.908s (-11.9% 🟢) 3.879s (-14.4% 🟢) 0.971s 8 1.08x
▲ Vercel Nitro 3.162s (-9.2% 🟢) 4.024s (-13.7% 🟢) 0.862s 8 1.17x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.073s 4.581s 0.509s 7 1.00x
💻 Local Next.js (Turbopack) 7.293s 7.765s 0.473s 4 1.79x
💻 Local Express 8.111s (+20.2% 🔺) 9.022s (+28.7% 🔺) 0.911s 4 1.99x
💻 Local Nitro 8.114s (+19.1% 🔺) 8.770s (+21.6% 🔺) 0.656s 4 1.99x
🌐 MongoDB Next.js (Turbopack) 9.786s 10.352s 0.566s 3 2.40x
🐘 Postgres Express 49.129s (~) 50.113s (+2.0%) 0.984s 1 12.06x
🐘 Postgres Nitro 54.036s (+4.1%) 54.120s (+3.8%) 0.084s 1 13.27x
🐘 Postgres Next.js (Turbopack) 56.399s 57.129s 0.730s 1 13.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 7.517s (+131.1% 🔺) 8.475s (+94.2% 🔺) 0.958s 4 1.00x
▲ Vercel Next.js (Turbopack) 9.181s (+130.3% 🔺) 10.029s (+81.7% 🔺) 0.848s 3 1.22x
▲ Vercel Nitro 9.329s (+135.6% 🔺) 10.653s (+114.4% 🔺) 1.324s 4 1.24x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.141s 1.002s 0.011s 1.016s 0.875s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.146s 1.000s 0.001s 1.007s 0.860s 10 1.04x
💻 Local Nitro 0.170s (+49.3% 🔺) 1.003s (~) 0.011s (+19.8% 🔺) 1.017s (~) 0.847s 10 1.21x
💻 Local Express 0.171s (+55.4% 🔺) 1.002s (~) 0.012s (+30.3% 🔺) 1.017s (~) 0.846s 10 1.21x
🌐 MongoDB Next.js (Turbopack) 0.481s 0.963s 0.001s 1.008s 0.527s 10 3.42x
🐘 Postgres Next.js (Turbopack) 0.857s 0.682s 0.001s 1.010s 0.153s 10 6.08x
🐘 Postgres Express 1.459s (-36.5% 🟢) 1.651s (-39.9% 🟢) 0.001s (+9.1% 🔺) 2.012s (-33.3% 🟢) 0.553s 10 10.35x
🐘 Postgres Nitro 2.037s (+46.9% 🔺) 2.555s (+54.4% 🔺) 0.002s (+15.4% 🔺) 2.815s (+39.9% 🔺) 0.778s 10 14.45x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.273s (+7.6% 🔺) 2.801s (+3.9%) 0.248s (-8.5% 🟢) 3.605s (-0.7%) 1.333s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.290s (+4.8%) 3.035s (+12.2% 🔺) 0.173s (-34.8% 🟢) 3.778s (+5.7% 🔺) 1.488s 10 1.01x
▲ Vercel Nitro 2.376s (+7.7% 🔺) 2.725s (-6.9% 🟢) 0.232s (-17.5% 🟢) 3.562s (-6.6% 🟢) 1.185s 10 1.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 8/12
🐘 Postgres Express 8/12
▲ Vercel Express 7/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 🌐 Redis 9/12
Nitro 💻 Local 11/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds comprehensive unit tests for the getHeadersFromPayload function introduced in PR #1098, which auto-injects workflow and step ID headers into VQS queue messages. The tests verify that headers are correctly extracted from queue payloads and propagated through both the initial queue() call and the delayed re-enqueue path in createQueueHandler.

Changes:

  • Added 6 new test cases covering workflow payload header injection, step payload header injection, health check payloads (no headers), caller header override precedence, and delayed re-enqueue scenarios for both workflow and step payloads

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@pranaygp pranaygp merged commit ae6b81c into main Feb 20, 2026
105 of 107 checks passed
@pranaygp pranaygp deleted the pg/add-vqs-header-injection-tests branch February 20, 2026 02:06
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.

2 participants