Expanded the testcase for GRPlatform>>secureHashFor:

[jbrichau]

The method GRPlatform>>secureHashFor: accepts both a String and a ByteArray as argument. The contents of the ByteArray can be any sequence of bytes, so it should not represent a valid UTF8 encoded String (for example).

In this PR, we extend the test case to also cover the use of a ByteArray.

In Seaside, all invocations of the method always passed a String instance as argument, until the e-tag implementation for the file libraries, which also uses it to generate a hash for any served file, which may include binary files (e.g. images). See SeasideSt/Seaside#1325.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.59%. Comparing base (5e8378a) to head (8f04339).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #182      +/-   ##
==========================================
+ Coverage   85.58%   85.59%   +0.01%     
==========================================
  Files        2050     2050              
  Lines       14100    14110      +10     
==========================================
+ Hits        12067    12077      +10     
  Misses       2033     2033              

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