Re: Testing Javascript

On Thu, 26 Jun 2008 07:47:11 -0000, [email protected] wrote:
>On 07:34 am, [email protected] wrote:
> [snip]
>>I think you've focused mostly on the unit testing stuff I worked on
>>ages back. ISTR you have any integration tests for JS stuff that talk
>>to the server? (I definitely recall big testing pages that took ages
>>to load). Do you still do that? How does it work?
>
>There are still nits for nevow itself (athena, really), although they don't 
>integrate with the buildbot and I haven't worked on that code in a while. 
>Technically there are nits for a bunch of Mantissa and Quotient 
>functionality, but all new code being written in those areas has JS unit 
>tests instead.  It may be getting to be time to delete the ones that are 
>still in the tree.

Nits are useful for testing the stuff that you can only test in a browser.
They could be even more useful if nit had a bunch more features, but as it
is now is basically good enough to live with.

Even with more features, writing Nits for Mantissa or Quotient would be
wrong.  Only Nevow needs nits, because only Nevow has any business doing
things that can only be tested in a browser.  Anything higher level should
be using Nevow APIs, and any Nevow API can be mocked and tested outside of
a browser.

Jean-Paul