You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've gotten an enterprise application up and running with this style guide. I'm finding the documentation lacking for testing these modules. It is not clear if there is a test runner per component/per app/per module etc.. Is this beyond the scope of this style guide? a testing strategy seems critical.
The text was updated successfully, but these errors were encountered:
Testing is completely up to you, the Angular docs suggest Karma/Jasmine though. It's un-opinionated here due to the vast amount of tooling you can use so that call is based on your project setup (i.e. Grunt/Gulp/Webpack/etc). Testing can be done on specific modules alone, you can fetch them all via globbed strings such as /app/**/**.spec.js to just grab your test files for running against. Hope that helps!
I've gotten an enterprise application up and running with this style guide. I'm finding the documentation lacking for testing these modules. It is not clear if there is a test runner per component/per app/per module etc.. Is this beyond the scope of this style guide? a testing strategy seems critical.
The text was updated successfully, but these errors were encountered: