Closed jonathanp62 closed 1 month ago
Results are in Temp/aes-256-testing on the studio.
Unit testing is flaky on the first run.
I think this was fixed by 1) correcting the way test resources are loaded using the classloader and 2) by not using the classloader to access a newly encrypted file that had to be immediately decrypted in order to compare before and after checksums.
Test the three target files individually. Keep track of SHA-256 checksums. Zip the three target files and keep track of its SHA-256 checksum.