Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

QUnit's "asyncTest" never returns, only in PhantomJS #11200

Closed
siovene opened this issue Apr 3, 2013 · 4 comments
Closed

QUnit's "asyncTest" never returns, only in PhantomJS #11200

siovene opened this issue Apr 3, 2013 · 4 comments
Labels

Comments

@siovene
Copy link

siovene commented Apr 3, 2013

Hi,
I'm trying to run my unit tests in PhantomJS, but I hit a stumbling block. While everything works in Chrome, QUnit's asyncTest never returns in PhantomJS.

I have written some minimal code to reproduce the issue. Please clone this repository:

https://github.com/siovene/phantomjs-async-test

and then run phantomjs test/phantomjs-index.js

I've tried on PhantomJS 1.6 and 1.9.

Thanks for looking,
Salvatore.

@JamesMGreene
Copy link
Collaborator

I'm not going to say that this is your actual problem (particularly since I am mobile ATM and can't test it) but you are technically using an incorrect protocol here. It might be your problem, though, as WebKit core seems to be much less robust than its derivatives (e.g. Chrome) at self-correcting these types of issues.

You have 'file://' + file but technically need 'file:///' + file (3 slashes). The 2-slash form is only valid if you specify the machine name (or localhost) as well, e.g. 'file://localhost/' + file.

@siovene
Copy link
Author

siovene commented Apr 3, 2013

Hi James, thanks for the reply. Actually file already includes a trailing slash, so the whole path comes out as:

file:///home/siovene/code/phantomjs-async-test/test/index.html

@JamesMGreene
Copy link
Collaborator

Oh sure, right, non-Windows OS. :)

@stale stale bot added the stale label Dec 27, 2019
@stale
Copy link

stale bot commented Dec 30, 2019

Due to our very limited maintenance capacity, we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed (see #15395 for more details). In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!

@stale stale bot closed this as completed Dec 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants