We are building a reasonably large project with a number of different modules. When the project is run in the browser (minified or not) there are no problems with dependency resolution and there is no particular order in which the files are loaded or concatenated together. However, when all of the files source are provided to the Karma test runner, the resolution of dependencies fails in multiple places. These can be resolved by manually specifying an order of inclusion but we would like to avoid doing so as it would become tedious and likely somewhat fragile. We have also tried to add angular-loader into the tests along with the Angular files when running with Karma but this does not seem to work.
Is there some aspect to dependency resolution when running in Karma that we are missing? Effectively these tests run in the browser anyhow, so it seems there shouldn't be a huge difference. Any help would be very appreciated. Thank you. -- ------------------------------ If you believe you have received this electronic transmission in error, please notify the original sender of this email and destroy all copies of this communication. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
