Closed greenkeeper[bot] closed 7 years ago
Update to this version instead 🚀
The new version differs by 6 commits ahead by 6, behind by 1.
b8cf1f0
0.4.1
94f9cab
0.4.0
0fad897
Allow reporting of client console logging (#116)
138fa7f
Merge pull request #108 from bitovi/107-document-es6-coverage
6a35fbc
add es6 note and coverage example
7f3357d
Merge pull request #105 from bitovi/babel-plugin-istanbul
false
See the full diff
Update to this version instead 🚀
Prevent browser caching
also Add warning/autofix for missing doctype
The new version differs by 7 commits.
6caaae6
0.5.1
8df985f
Fix README badges (#132)
b0d6ae1
Readme rewrite (#126)
3cb4ab2
Prevent browser caching (#131)
248f6ef
Add warning/autofix for missing doctype (#130)
4b97feb
Merge pull request #129 from bitovi/fix-licence-field
25e506f
Make package.json license a valid SPDX license expression
See the full diff
Update to this version instead 🚀
In v0.6.0, I mistakenly used an object to the timeout error message which made timeout errors look like:
1) General error http://localhost:3996/test/index.html?__token=5ga9ch on {"browser":"firefox"}:
Error: Browser timed out within [object Object] seconds
That is fixed. The README was also updated with a comment on the recommended Testee testing workflow.
The new version differs by 12 commits.
dee47fa
0.6.1
c98c31d
Add note about development workflow (#139)
85c5cc2
Fix timeout variable (#140)
bc75724
0.6.0
08fb2b7
Use native Promises, remove Q dependency (#135)
7bbd009
Deprecate grunt task (#133)
e8b25ac
Merge pull request #119 from bitovi/greenkeeper/initial
6af2fe7
Merge branch 'master' into greenkeeper/initial
76ad59a
sticking with qunit 1.x for now
dc4c47b
Add UnhandledPromiseRejectionWarning help (#138)
7260ecb
docs(readme): add Greenkeeper badge
65c5c80
chore(package): update dependencies
See the full diff
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.
Release Notes
v0.4.0Support for Code Coverage when using ES6:
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](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: