test: refactor test-whatwg-webstreams-encoding to be shorter

[hidaviddong]

Use a forEach loop for assert.throws statements, improving code readability.

[lpinca]

@hidaviddong please remove the merge commit.

[hidaviddong]

@hidaviddong please remove the merge commit.

done

[richardlau]

Use a forEach loop for assert.throws statements, improving code readability.

This will make diagnosing any failures harder as the stack traces will now point to the loop without an indication of which iteration of the loop failed.

[hidaviddong]

Use a forEach loop for assert.throws statements, improving code readability.

This will make diagnosing any failures harder as the stack traces will now point to the loop without an indication of which iteration of the loop failed.

Do I need to add a stack trace? like done in #45146

[richardlau]

Use a forEach loop for assert.throws statements, improving code readability.

This will make diagnosing any failures harder as the stack traces will now point to the loop without an indication of which iteration of the loop failed.

Do I need to add a stack trace? like done in #45146

I think that would work.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.31%. Comparing base (4ce9864) to head (9738074).
Report is 737 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #54569 +/- ##
==========================================
- Coverage 87.33% 87.31% -0.03% 
==========================================
Files 649 649 Lines 182623 182755 +132 Branches 35041 35051 +10 ==========================================
+ Hits 159498 159575 +77 - Misses 16400 16452 +52 - Partials 6725 6728 +3 

see 54 files with indirect coverage changes

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/61672/ 💛

[hidaviddong]

I see a CI failure, but I'm not sure what caused it. Do I need to change anything?

[nodejs-github-bot]

Landed in 291d90a