We tried to reproduce the issue on our test systems as well as reviewed the code of test script 020.js.
We can't find a way the script is printing an error and exists, excepts for a generic error catch. In order to identify the issue in the code, could you please provide the error output of script 020?

Send email to reporter - if no response will close as not repeatable

I answered the questions of Alexander Allmendinger on 10.9.2019 by email already. See attachment 20190910_CTT_Report.pdf.
If 020.js is not executed, the 022.js is ok. See attachment 020.js.jpg in Debug Run1.
The error in 022.js only occures if 020.js goes wrong. See attachment 020.js.jpg in Debug Run2.
The 020.js goes wrong in this older version of OPC server because the BadNotSupported for IndexRange. See attachment 020.js-wireshark.jpg.

020.js-wireshark.jpg (215,852 bytes)   

020.js-wireshark.jpg (215,852 bytes)   

The error occurrs when the server returns an empty value in a PublishResponse. If toByteStringArray() gets called on this empty Value, the script returns an unexpected error when trying to access the result.
Code was extended to check if the returned value in the PublishResponse is empty before calling toByteStringArray() and print an error if it is.

reviewed issue in call, agreed to changes and closed issue