- From: Clint Hill <clint.hill@gmail.com>
- Date: Tue, 08 Jan 2013 13:04:42 -0700
- To: Mat Scales <mat@wibbly.org.uk>, "<,public-nextweb@w3.org>," <public-nextweb@w3.org>
Received on Tuesday, 8 January 2013 20:04:27 UTC
+1 on grunt +1 on qunit Grunt will also help us resolve the AMD/build question from the other thread. From: Mat Scales <mat@wibbly.org.uk> Date: Tuesday, January 8, 2013 12:52 PM To: "<,public-nextweb@w3.org> <mailto:public-nextweb@w3.org>> ," <public-nextweb@w3.org> Subject: Re: Tests Resent-From: <public-nextweb@w3.org> Resent-Date: Tue, 08 Jan 2013 19:52:55 +0000 If we use grunt (which I HIGHLY recommend) then it is trivial to get set up with automated tests using phantomjs, which is awesome. For actual test framework qunit is simple and effective, but I also like mocha+chai. On 8 January 2013 19:45, Marcos Caceres <marcos@marcosc.com> wrote: > Hi All, > The code I proposed currently lacks tests (on purpose!) as I was not sure what > we should use for that and how we should structure them. > > That is, obviously, for each WebIDL type we should have a set of tests that > checks the conversion is happening as expected. > > Any guidance on how to proceed would be great! > > -- > Marcos Caceres > > >
Received on Tuesday, 8 January 2013 20:04:27 UTC