This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of grunt-contrib-qunit.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
grunt-contrib-qunit just published its new version 2.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of grunt-contrib-qunit. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 53 commits .
b9522f4
v2.0.0
f45b682
Remove usage of
QUnit.jsDump
353a7a8
Upgrade qunitjs to 2.3.0 (#123)
f28e09d
adding an Introduction to the README (#140)
5085bf9
v1.3.0 release (#138) r=@leobalter,@Arkni
347c126
Implement support for todo tests and revamp reporting logic (#137)
0a4834f
Update link to PhantomJS API
2471bb8
Fix typo
b36aa1a
Add note about min version of QUnit required to use the CLI flags
323e198
minor tweaks
461e408
Add ability to run tests in seeded-random order through
--seed
flag36616b1
v1.2.0
d31dec4
Merge pull request #119 from samkirkpatrick/master
8911a47
Generate the hashes only once, and reuse them for every url
dadf6ac
Document
--modules
command line optionThere are 53 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.