Closed FrankVisuals closed 1 year ago
Thanks for reporting the issue, can you tell me more about your configuration ? how are the files instrumented ? can you share the report.html ?
(Since you blanked out the path, you might not want to share the report.html which contains path)
I need to understand why the coverage is getting .ts files, I suspect that - during transpiling - the JS code is automatically instrumented. It also means that you use the remote
mode (--url
).
I shall probably test if the file path is reachable before trying to download it, that would solve this issue. Can you confirm that the coverage files (.nyc_output
) contain absolute path ?
In the meantime, to unblock your workflow, you may use version 3.3.1
using npm i -g ui5-test-runner@3.3.1
reproduced locally, looks like the assumptions are correct.
@FrankVisuals I believe the version 3.3.4 addresses this issue, can you confirm the problem is either solved or still occurring ?
Sorry for my late response @ArnaudBuchholz
I've just tested it with version 3.3.4 - it works now! Thanks for the provided fix
Since version 3.3.1 (3.3.2 did also not work) I received the following error when running my tests:
After some investigation I found out that in version 3.3.0 it still worked. I identified these changes as root cause: https://github.com/ArnaudBuchholz/ui5-test-runner/commit/9fdfba049c0a95077f41bfc6526234f9935ab9f5
The request that tries to read the files has the absolute path to the file set as URI path
Therefore it leads to 404