Skip to content
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

Documentation is missing how are spec files collected and ran using this structure #139

Open
dougrchamberlain opened this issue Nov 22, 2016 · 1 comment

Comments

@dougrchamberlain
Copy link

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.

@toddmotto
Copy link
Owner

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants