getProxyUrl doesn't resolve relative paths for special page URLs

[benmonro]

What is your Test Scenario?

when using the clientScripts in a testcafe config, if you then try to use t.navigateTo an error occurs. all details and repro steps can be found here: testing-library/testcafe-testing-library#222

What is the Current behavior?

error

What is the Expected behavior?

no error

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):

Your complete configuration file (if any):

Your complete test report:

Screenshots:

Steps to Reproduce:

1. Go to my website ...
2. Execute this command...
3. See the error...

Your Environment details:

• testcafe version:
• node.js version:
• command-line arguments:
• browser name and version:
• platform and version:
• other:

[Ogurecher]

Hello @benmonro,
Thank you for your report. I've reproduced this issue. We'll update this thread once it's fixed.

[miherlosev]

Steps to reproduce:

• git clone https://github.com/SamuelDavis/testing-library-testcafe-integration;
• cd testing-library-testcafe-integration;
• npm install;
• npx testcafe chrome tests.js;

[AndreyBelym]

I would say that getFirstDestUrl function works correctly in this case since the error that we use to parse stack is originated from the service TestCafe script - the injected client script, not by some page script, and doesn't contain any proxied URL:

Error
    at beforeTransform (http://172.22.14.234:59840/hammerhead.js:28337:19)
    at transformProgram (http://172.22.14.234:59840/hammerhead.js:28409:9)
    at processScript (http://172.22.14.234:59840/hammerhead.js:27817:46)
    at FunctionWrapper (http://172.22.14.234:59840/hammerhead.js:19904:121)
    at http://172.22.14.234:59840/custom-client-scripts/__node_modules_@testing-library_dom_dist_@testing-library_dom_umd_js:14115:7
    at createCommonjsModule (http://172.22.14.234:59840/custom-client-scripts/__node_modules_@testing-library_dom_dist_@testing-library_dom_umd_js:129:7)
    at http://172.22.14.234:59840/custom-client-scripts/__node_modules_@testing-library_dom_dist_@testing-library_dom_umd_js:13420:19
    at http://172.22.14.234:59840/custom-client-scripts/__node_modules_@testing-library_dom_dist_@testing-library_dom_umd_js:5:29
    at http://172.22.14.234:59840/custom-client-scripts/__node_modules_@testing-library_dom_dist_@testing-library_dom_umd_js:6:2"

I think that getProxyUrl is the real culprit here. It returns incorrect results when handling relative URLs called on the proxied about:blank page. Compare this:

[miherlosev]

@AndreyBelym is right.

In case, if the stack doesn't contain the tested page URL, we are trying to calculate it using the getProxyUrl('./') function call.