-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add timeout before starting qunit #107
Conversation
Is this the right approach, though?
PS. would it be possible for the tests to cover this case?
…On Tue, Apr 17, 2018 at 11:57 AM Johann-S ***@***.***> wrote:
In this PR QUnit removed their timeout : qunitjs/qunit#1246
<qunitjs/qunit#1246> so we try to run unit tests
before they are loaded, that leads to error like No tests were run.
Related to #103 <#103>
/CC @XhmikosR <https://github.com/XhmikosR> @dignifiedquire
<https://github.com/dignifiedquire>
------------------------------
You can view, comment on, or merge this pull request online at:
#107
Commit Summary
- Add timeout before starting qunit
File Changes
- *M* src/adapter.js
<https://github.com/karma-runner/karma-qunit/pull/107/files#diff-0>
(5)
Patch Links:
- https://github.com/karma-runner/karma-qunit/pull/107.patch
- https://github.com/karma-runner/karma-qunit/pull/107.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#107>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVVtf8sMjFka8UxGW0RtdXMFnTwVYg0ks5tpa6CgaJpZM4TX5gH>
.
|
It was the approach used by QUnit, and with that delay our tests can run, I updated my commit and tests passed |
Yes, I understand that :)
What I'm saying is that since they removed the delay, something else must
change here to comply with that.
PS. with tests I meant the tests in this repo which didn't catch this case
since they have been always green.
…On Tue, Apr 17, 2018 at 12:12 PM Johann-S ***@***.***> wrote:
It was the approach used by QUnit, and with that delay our tests can run,
I updated my commit and tests passed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVVtRpax5hC2wA-3-lvFCunxf_qhIl5ks5tpbH4gaJpZM4TX5gH>
.
|
Nope, the other changes must be in our unit tests but not here, because it's in the internal logic of QUnit not in the public API. They were green because we tested with just one file, so it's pretty hard to test that, plus in our use case we load files from CDN EDIT: ping @dignifiedquire |
Ping @dignifiedquire |
I added a unit test which reproduce this use case |
What are you npm usernames and I can add you for karma-qunit (although I
think johnjbarton is in the process pushing to npm right now)...
…On Wed, May 2, 2018 at 3:05 PM, XhmikosR ***@***.***> wrote:
@Johann-S <https://github.com/Johann-S>: do you have access to the npm
account too? If not maybe ask @zzo <https://github.com/zzo> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAr0Gu0ehvG4zGdlvb3Ws7kIY9tBEbqDks5tui2egaJpZM4TX5gH>
.
|
@zzo my username is Thank you 👍 |
In this PR QUnit removed their timeout : qunitjs/qunit#1246 so we try to run unit tests before they are loaded, that leads to error like
No tests were run.
Fixes: #103
/CC @XhmikosR @dignifiedquire