Regarding running javascript tests, could we consider something like rhino? Just an off the top of my head suggestion. Would avoid node.js, not sure if it's an improvement though.
Matt Lauber On Wed, Apr 16, 2014 at 9:20 PM, Russell Keith-Magee < [email protected]> wrote: > > On Thu, Apr 17, 2014 at 5:57 AM, Trey Hunner <[email protected]> wrote: > >> I saw a previous discussion about JavaScript testing in Django but it >> looks like there hasn't been any progress in a few years. >> >> Some of my thoughts on this issue: >> >> This would require choosing a JavaScript testing framework. There are >> many good ones out there. A popular one should probably used for easier >> community support. >> >> Unit testing JavaScript (ideally) should not require running the Django >> server. >> >> JavaScript tests will probably require introducing Node.js into the >> automated testing process. Tests can be run manually from the browser, but >> automated JavaScript tests tend to require Node.js and sometimes PhantomJS >> (for headless testing). >> >> The JavaScript tests should be run as part of the CI testing process. If >> the tests are run standalone this should be easy to do using a single >> command (possibly requiring grunt or a similar task runner). >> >> This seems like it would be a big change, but I think it could be done in >> small steps. Setting up the testing framework is the first big step. >> >> What do others think about this issue? >> > > I have two thoughts: > > 1) More testing doubleplus good. :-) > > 2) Is there anything that can save us from the Node.js kudzu? :-) > > As with your previous question about linting, I don't have any firm > opinions about this, beyond "Yes, we should do it". > > My suggestion here would be to proceed as if we all agree that this is a > good idea (more testing good, etc), and make a concrete proposal. It's a > lot easier to discuss a concrete proposal than to just kick around > buzzwords and hope some of them stick :-). > > You've definitely identified that this is a long term project; so if you > can lay out a map for the way forward, with an indication of the end goal, > that would be a fantastic start IMHO. > > Yours, > Russ Magee %-) > > > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" 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/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAJxq84_2u%3DtUpEKwOQ0fPDFcOB80w0K%3Dh%2By_Kg6DM7T8LkSPOg%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CAJxq84_2u%3DtUpEKwOQ0fPDFcOB80w0K%3Dh%2By_Kg6DM7T8LkSPOg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CA%2BU9Apc5e_w7S3WGpDVd70oEGSL9rk1zo52w9-1KLUanYNeTFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
