-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update testee to the latest version 🚀 #239
base: master
Are you sure you want to change the base?
Conversation
Version 0.4.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits ahead by 6, behind by 1.
false See the full diff |
Version 0.5.0 just got published.Update to this version instead 🚀 Release Notesv0.5.0 |
Version 0.5.1 just got published.Update to this version instead 🚀 Release NotesPrevent Browser CachingPrevent browser caching CommitsThe new version differs by 7 commits.
See the full diff |
Version 0.6.1 just got published.Update to this version instead 🚀 Release NotesTimed ObjectiveIn v0.6.0, I mistakenly used an object to the timeout error message which made timeout errors look like:
That is fixed. The README was also updated with a comment on the recommended Testee testing workflow. CommitsThe new version differs by 12 commits.
See the full diff |
Version 0.7.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Version 0.8.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Version 0.8.1 just got published. |
Update to this version instead 🚀 Release Notes for Enable reporterOptions parameter to the specified ReporterEnable reporterOptions on testee specified reporters like XUnit reporter, fixes issue #180. CommitsThe new version differs by 7 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 5 commits.
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.
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 🌴