test(node): Make amqplib integration test order-independent

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.

[mydea]

Summary

Applies the same fix as #21534 (amqplib v1) to the non-versioned amqplib auto-instrumentation test (suites/tracing/amqplib/test.ts), which has the identical flaky pattern.

Root cause

The test asserted the producer (root span) and consumer (queue1 process) transactions in a fixed order using two sequential .expect() callbacks. The runner matches expected envelopes strictly FIFO, but the producer and consumer are independent traces flushed independently, so their arrival order at the test server isn't guaranteed. When the consumer envelope arrived first, the first assertion (expect(transaction.transaction).toEqual('root span')) failed against the consumer transaction.

Fix

Use the established collect-then-assert pattern (same as #21534 and the kafkajs test): push both transactions into an array, then look them up by transaction name and assert once both have arrived. All original assertions (producer name + span count + PRODUCER span shape, consumer CONSUMER trace context) are preserved — only the order dependency is removed.