Re: Does the javascript test runner need attention?

2016-12-19 Thread 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.

On Thursday, August 25, 2016 at 11:27:39 AM UTC-4, Tim Graham wrote:
>
> 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
>
> On Thursday, August 25, 2016 at 9:31:08 AM UTC-4, Josh Smeaton wrote:
>>
>> 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
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d377b3ce-7ae9-4675-bb1a-2c47d066f1dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Does the javascript test runner need attention?

2016-08-25 Thread 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

On Thursday, August 25, 2016 at 9:31:08 AM UTC-4, Josh Smeaton wrote:
>
> 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
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d41a4227-9979-47b9-8260-ae45d15415ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.