test(cbor): empty string being excluded from expected result

[BlackAsLight]

Closes: #6102

The expected result was filtering out empty strings provided in the input text, while CborTextEncoderStream doesn't remove them. The test appeared flaky because of the randomness of the test. In the event the first random chose zero (which is a 1 in 24 chance), an empty string would be one of the chunks. An empty string is encoded as byte 96.

Lowering the size of the strings had no effect on the flakiness of the tests, but I am assuming that's why they were lowered in the first place.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.57%. Comparing base (a4cd8af) to head (e407c93).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6106      +/-   ##
==========================================
+ Coverage   96.55%   96.57%   +0.02%     
==========================================
  Files         534      534              
  Lines       40589    40589              
  Branches     6093     6095       +2     
==========================================
+ Hits        39190    39199       +9     
+ Misses       1355     1346       -9     
  Partials       44       44              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kt3k]

The expected result was filtering out empty strings provided in the input text, while CborTextEncoderStream doesn't remove them. The test appeared flaky because of the randomness of the test. In the event the first random chose zero (which is a 1 in 24 chance), an empty string would be one of the chunks. An empty string is encoded as byte 96.

Thanks for looking into this!

[kt3k]

LGTM