On Fri, Aug 15, 2008 at 1:40 PM, Garrett Smith <[EMAIL PROTECTED]> wrote:
[snip] >> There remain challenges, in particular getting off of the untestable >> and increasingly unwieldy ES1-3.x spec formalism. > > Unit tests: > * help developer understanding > * provide examples for discussion > * provide conformance suite for implementors > * define boundaries on what is and what is not supported* > > The tests could use a custom test runner or use an existing one. It > would be useful if the testrunner could be run in a browser. > > It would be helpful to have code comments in the tests, indicating > exactly which rules of the spec are being tested, so that the reader > can quickly go to that section of the spec (spec in HTML). > > Real code examples in the spec would be useful, too. I can easily see > a bookmarklet used to capture and execute the example selection of the > spec. This seems like "literate programming" to me where the program is a set of unit tests. [snip] Peter _______________________________________________ Es4-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es4-discuss
