Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds bower-managed QUnit testing for #127. I am not a particular fan of QUnit, but it seemed like the simplest thing to set up for this kind of use case.
The fix was indeed just turning
standalone
back on, which I thought I had tried, but so it goes. But the important thing is the test and integration into gulp, I suppose.It does make the build a lot longer, but I wanted to make sure travis liked it. Perhaps putting standalone behind a flag? Since the fix is so simple but expensive, it really doesn't need to be run all the time. I am not much of a gulp wizard, so I don't know how one would go about doing that... environment variables are sometimes the easiest way :P
Also, I found it a bit odd that
test
didn't include adist
precursor... I've added it crudely to package.json, but let me know why you wouldn't want travis to ensure the build is working :)