On Windows, the filesystem path may be limited to 260 characters.
With generated test names this is often exceeded which causes report pages not being shown without warning.
Is your feature request related to other issues/PRs?
no
Describe the solution you'd like
Add an option to add JavaScript code that checks if a file link would exceed the 260 character limit and show a warning.
Checking the href attribute of an anchor tag should show the resolved absolute path if the URL is of file origin
document.querySelectorAll("a[href]").forEach(function (a) {
var raw = a.getAttribute("href");
// ...
}
Describe alternatives you've considered
Checking this when generating doesn't help, because the report content may be moved to deeper nested folder, which then exceeds the total path length limit.
Additional context
On Windows, the filesystem path may be limited to 260 characters.
With generated test names this is often exceeded which causes report pages not being shown without warning.
Is your feature request related to other issues/PRs?
no
Describe the solution you'd like
Add an option to add JavaScript code that checks if a file link would exceed the 260 character limit and show a warning.
Checking the
hrefattribute of an anchor tag should show the resolved absolute path if the URL is offileoriginDescribe alternatives you've considered
Checking this when generating doesn't help, because the report content may be moved to deeper nested folder, which then exceeds the total path length limit.
Additional context