Skip to content
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

need a technique for supporting asynchronous tests #3

Open
paulirish opened this issue Sep 26, 2010 · 3 comments
Open

need a technique for supporting asynchronous tests #3

paulirish opened this issue Sep 26, 2010 · 3 comments
Labels

Comments

@paulirish
Copy link
Collaborator

data URI is one test where async is required

@peol
Copy link
Contributor

peol commented Sep 27, 2010

Yeah, I think QUnit would be pretty ace to have here, or implement something like this from scratch that is simple and lightweight (which might be hard).

@phiggins42
Copy link
Owner

yah, doh has a super lightweight dojo.Deffered version (promises). Something following that simple API would be a win, though adds complexity that anything depending on it couldn't reliably use the test until after the callback. something like has("someaynctest").callback(fnForTrueCase).error(fnForFalseCase); with the ultimate end result being has("someasynctest") will be a new dfd (eg: always async)

or should async tests resolve to truthy values once completed? or, when(has("someasynctest", function(result){ ... }) or should it be a new/extra API (I can't imagine tooooo many fd tests needing to be async)

@jdunck
Copy link

jdunck commented Oct 13, 2010

Here's another test that would require async support:
http://heydanno.com/blog/2010/03/07/detecting-transition-event-support/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants