Update ember-a11y-testing to the latest version 🚀 #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
|
This slightly changes the default behavior- acceptance tests will no longer run accessibility audit by default (see https://github.com/ember-a11y/ember-a11y-testing#testing-usage ). Since we don't have any acceptance tests in the demo app, the impact here is minimal. However, when I try to make an acceptance test with deliberate errors (and run in |
abought
force-pushed
the
greenkeeper/ember-a11y-testing-0.4.0
branch
from
f6b9a05 to
6327f8c
Compare
Version 0.4.1 just got published. |
Version 0.4.2 just got published.Update to this version instead 🚀 Release Notes0.4.2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ember-a11y-testing 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 ember-a11y-testing.
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
0.4.0Commits
The new version differs by 22 commits .
50633a3Release v0.4.02c05c28Merge pull request #72 from trentmwillis/options-argee29e80Update readme with new features/info37f9c81Support passing options as a single argument to a11yAudit09be645Merge pull request #70 from sarbbottam/feat/opt-in5ab9e75feat(a11yAudit): opt in to a11yAudit9ebea55Merge pull request #71 from ember-a11y/test-fix9419320Fix axe-component error test47c867aMerge pull request #67 from samselikoff/patch-19765119Ensuresupercall is boundedfdd686dReleased v0.3.0df8ee9bMerge pull request #66 from trentmwillis/eslintcc2541fReplace jshint with eslintc91f2d9Merge pull request #64 from trentmwillis/remove-auto-runb5ff7e6Released v0.2.2There are 22 commits in total. 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 🌴