feat(testing-karma): added base karma test configs #58
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
LarsDenBakker
force-pushed
the
feat/update-karma-helpers
branch
from
5212268
to
b51ea6f
Compare
daKmoR
force-pushed
the
feat/update-karma-helpers
branch
3 times, most recently
from
2aaeb7e
to
2a15f9a
Compare
daKmoR
force-pushed
the
feat/update-karma-helpers
branch
3 times, most recently
from
1b2fc98
to
d69e521
Compare
daKmoR
force-pushed
the
feat/update-karma-helpers
branch
from
d69e521
to
ec44d2e
Compare
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.
Depends on #57
Adds karma config presets to run karma tests with web components. The regular test config runs on all modern browsers (latest chrome, firefox, safari). For older browsers and browsers that don't support web components, the es5 config should be used.
This significantly speeds up testing, as you're not compiling everything to es5 and loading polyfills all the time.
For these kinds of projects, I really like a README.md as it's the best accessible for developers. It feels like the current setup of the docs is a bit disconnected and/or not immediately obvious where to find. What do you think about adding brief examples in the readme?