On Mon, Sep 12, 2011 at 11:11:07PM +0930, David Kettler wrote: > This provides summary results such as the following: > > % conkeror -q -e 'url_remoting_fn = load;' $PWD/tests/simple/*.js -f > walnut-summarize > ... > Totals: 58 run, 0 failed in 15 suites >
Very interesting idea. Could walnut define a command-line switch, instead of providing an interactive command? Also, would you mind making the patch conform to our whitespace/style guidelines? Url for that is: http://conkeror.org/DevelopmentGuidelines The two points that apply (that I noticed) are: * in javascript objects, no space between the key and the colon...e.g: { foo: "bar" } * and the one rule that might drive some people crazy, but works well in practice is that long strings like docstrings, or inline functions that get passed to define_* or interactive forms only get indented by 4 spaces, instead of lining up with the opening paren of the function. Conkeror makes extensive use of this style in order to have a lisp-like declarative API. Just pretend these forms are macros because indenting them this way keeps the source code from running ridiculously far to the right. Incidentally, the first argument to these forms should be on the same line as the function name because it makes grepping easier. Example: -- John Foerch _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
