Update testee to the latest version 馃殌 #1169
Closed
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.
Version 0.4.0 of testee just got published.
The version 0.4.0 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 testee.
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.
Commits
The new version differs by 12 commits .
f7d8a96
0.4.0
84682ed
add troubleshoot:cache section
156a6da
fix caching/jasmine coverage bugs
4ce1214
resolved conflicts
3727c0b
using babel-plugin-istanbul for coverage instrumentation
a693817
Refactoring coverage tests
b468dfc
Creating separate blogpost modules for each test runner
5d69d54
Running coverage tests separately from other tests
e8296c9
refactoring coverage tests
ce3a1f7
running all tests
965ba4f
removing
/
from beginning of path so that babel-plugin-istanbul won't skip file92c244f
trying to use babel-plugin-istanbul for coverage instrumentation
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨