Repository navigation
Fix the unit-tests for on-demand password handling of encrypted attachments (issue 21425) - #21429
Conversation
β¦hments (issue 21425) These unit-tests used a PDF that prompted for password on document load, which meant that the on-demand password handling wasn't actually being tested as intended. Updating the unit-tests also caused the "re-prompts for encrypted attachments after incorrect passwords" test to fail, since the `INCORRECT_PASSWORD` password reason was being accidentally "swallowed" in the worker-thread.
Codecov Reportβ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #21429 +/- ##
==========================================
+ Coverage 89.74% 89.76% +0.01%
==========================================
Files 260 260
Lines 66007 66004 -3
==========================================
+ Hits 59241 59249 +8
+ Misses 6766 6755 -11
Flags with carried forward coverage won't be shown. Click here to find out more. β View full report in Codecov by Harness. π New features to boost your workflow:
|
β¦.js` file Currently the same code, for requesting the password from the main-thread, is now duplicated three times. Let's avoid that by moving the new `getPassword` helper function, added in the previous commit, and re-use that everywhere instead.
|
/botio browsertest |
From: Bot.io (Windows)ReceivedCommand cmd_browsertest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.193.163.58:8877/66c2a845bf81128/output.txt |
From: Bot.io (Linux m4)ReceivedCommand cmd_browsertest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/08cef37419a2f37/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/08cef37419a2f37/output.txt Total script time: 18.29 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/66c2a845bf81128/output.txt Total script time: 46.10 mins
|
These unit-tests used a PDF that prompted for password on document load, which meant that the on-demand password handling wasn't actually being tested as intended.
Updating the unit-tests also caused the "re-prompts for encrypted attachments after incorrect passwords" test to fail, since the
INCORRECT_PASSWORDpassword reason was being accidentally "swallowed" in the worker-thread.