Djangular supports developers writing karma using these two management commands:
makeangularsite creates karma config file templates that handle the djangular app pathstestjs will shell out to karma and run the appropriate config file
the first is in need of an update:
as karma is on 0.12 and djangular writes out a file that's no longer compatible (I believe we're writing out a 0.8-style file, but there was backwards incompatible change in 0.9 or 0.10)
the second could use some enhancements:
- the management command assumes that
karma exists on the path (which isn't typical when not installing using npm -g)
- there's no way to pass additional command line arguments to the
karma invocation, which is useful for having jenkins run against PhantomJS and then letting developers override this at their desktops to run Firefox/Chrome
- running
testjs assume's that you have a very particular working directory so it can find an app's config files. It would be convenient let testjs work no matter your working directory.
Djangular supports developers writing karma using these two management commands:
makeangularsitecreates karma config file templates that handle the djangular app pathstestjswill shell out tokarmaand run the appropriate config filethe first is in need of an update:
as karma is on 0.12 and djangular writes out a file that's no longer compatible (I believe we're writing out a 0.8-style file, but there was backwards incompatible change in 0.9 or 0.10)
the second could use some enhancements:
karmaexists on the path (which isn't typical when not installing usingnpm -g)karmainvocation, which is useful for having jenkins run against PhantomJS and then letting developers override this at their desktops to run Firefox/Chrometestjsassume's that you have a very particular working directory so it can find an app's config files. It would be convenient lettestjswork no matter your working directory.