cironunes / angular-testing-recipes Goto Github PK

Current status:

Best authoring practices in general

Directives can have isolate scope or not, transclude: true|'element' and some more variations. How should we approach this in the project?

• A file for each kind of property?
• A file for some combined properties?
• Should the basics be in a directives.js?

It's a nice idea to add the setup steps in the README file, explaining what you need to run the project.

We should make sure that we have no references to outdated recipes. Our recipes will be:

• Controllers
• Filters
• Services
• Decorators
• Directives
• E2E

Note that we spell them all in the plural.

TO DO:

• Rename Protractor to E2E
• Rename Service to Services
• Rename Controller to Controllers
• Remove jquery-events, use-of-promises and use-of-services
• Reorder the Table of Contents

Features:

• Run karma
• Add code coverage
• nghtml2js
• jshint

https://medium.com/@cironunesdev/how-to-unit-test-angularjs-decorators-67a28ef29e8d