@UlisesGascon
Thank you for your response.
The requested adjustments have been made.

The tests are failing due the changes on qs (see discussion on body-parser too expressjs/body-parser#687 (comment)).

  1) express.urlencoded()
       with extended option
         when false
           should parse multiple key instances:
     Error: expected '{"user":["Tobi","Loki"]}' response body, got '{"user":{"0":"Tobi","1":"Loki"}}'
      at Context.<anonymous> (test/express.urlencoded.js:106:12)
      at process.processImmediate (node:internal/timers:476:21)
      at process.callbackTrampoline (node:internal/async_hooks:128:17)
  ----
      at error (node_modules/supertest/lib/test.js:335:15)
      at Test._assertBody (node_modules/supertest/lib/test.js:206:16)
      at /home/runner/work/express/express/node_modules/supertest/lib/test.js:308:13
      at Test._assertFunction (node_modules/supertest/lib/test.js:285:13)
      at Test.assert (node_modules/supertest/lib/test.js:164:23)
      at Server.localAssert (node_modules/supertest/lib/test.js:120:14)
      at Object.onceWrapper (node:events:631:28)
      at Server.emit (node:events:517:28)
      at emitCloseNT (node:net:2221:8)
      at process.processTicksAndRejections (node:internal/process/task_queues:81:21)

cc: @expressjs/express-tc

Os testes estão falhando devido às alterações no qs (veja também a discussão sobre body-parser expressjs/body-parser#687 (comentário) ).

  1) express.urlencoded()
       with extended option
         when false
           should parse multiple key instances:
     Error: expected '{"user":["Tobi","Loki"]}' response body, got '{"user":{"0":"Tobi","1":"Loki"}}'
      at Context.<anonymous> (test/express.urlencoded.js:106:12)
      at process.processImmediate (node:internal/timers:476:21)
      at process.callbackTrampoline (node:internal/async_hooks:128:17)
  ----
      at error (node_modules/supertest/lib/test.js:335:15)
      at Test._assertBody (node_modules/supertest/lib/test.js:206:16)
      at /home/runner/work/express/express/node_modules/supertest/lib/test.js:308:13
      at Test._assertFunction (node_modules/supertest/lib/test.js:285:13)
      at Test.assert (node_modules/supertest/lib/test.js:164:23)
      at Server.localAssert (node_modules/supertest/lib/test.js:120:14)
      at Object.onceWrapper (node:events:631:28)
      at Server.emit (node:events:517:28)
      at emitCloseNT (node:net:2221:8)
      at process.processTicksAndRejections (node:internal/process/task_queues:81:21)

cc: @expressjs/express-tc

@UlisesGascon
Okay, based on this test failure, should we:

• align the test with the new behavior?
• or maintain compatibility with the current behavior?

These tests are basically just asserting on body-parser behavior due to the pass through, so we fix it in body-parser and take both updates at the same time

we have a PR to update body-parser #6972

@jonchurch
All right, I'll be waiting,
Thanks for your response.

It is expected that Node@16 and/or Node@17 can fail (legacy). So far Node@18 and ahead are working as expected.

I think it was due to caching issues that it kept failing; I reran the tests and now they pass.