Does the javascript test runner need attention?

[Josh Smeaton]

Hi All,

While building out a vagrant image for running django's tests (plug: https://github.com/django/django-box) I came across a problem trying to run the javascript tests as defined by the tox.ini file. It ended up being the same problem as raised in https://code.djangoproject.com/ticket/25803. The fix to that ticket was to update the package.json dependencies listing npm as < 3.0.0, but I'm wondering if there's a longer term solution we're going to need to look at.

https://github.com/ModelN/grunt-blanket-qunit appears to be abandoned and is probably the main cause of us requiring npm version 2. Maybe we could look at separate packages for generating code coverage and running qunit tests? Does that sound right? I'm happy to open a ticket to track this, but just wanted to see if it's needed or already on someones radar.

Cheers

[Tim Graham]

Trey Hunner said [0], "Blanket and qunit are the only real requirements here. We may be able to switch away from Grunt and use those together in a more manual fashion so requirements can be upgraded easily."

[0] https://github.com/django/django/pull/4889#issuecomment-219921988

[Tim Graham]

Hopefully the situation is a bit improved after https://github.com/django/django/commit/10278885fd909085bd76ccc1690a979582455f9e

We had to make this update as the old pinned phantomjs version doesn't support SHA256 SSL certs and thus couldn't fetch https://cdnjs.cloudflare.com/ajax/libs/openlayers/2.13.1/OpenLayers.js after cloudflare updated their cert today.