News for hackers. Stuff that matters.
Re:Kent Beck: “I get paid for code that works, not for tests... by kazinator on Thursday December 08, 2016 @09:57PM (#13136327)
I'd wait until the Lisp interpreter works significantly and then write reasonable code in Lisp like:

  (it (atom 'foo) t)
If it fails, it just says something like:

  test failed: (atom 'foo) returned nil; expected t.
So no need to have a string there. Save the "blub-level" testing for things that are not testable through Lisp. (Or, really, things you are justified in not wanting to expose such that they are testable.)

(Sure, it could be the case that both the interpreter are wrong, and the atom function are wrong such that the test passes. That level of breakage isn't likely going to pass much of a significantly detailed test suite.)

Re:Kent Beck: “I get paid for code that works, not for tests... by wolfgang42 on Friday December 09, 2016 @11:08AM (#13139510)
If I'd waited until the interpreter to work before I wrote tests, I'd never have gotten a working interpreter. For atom the implementation is obvious, but the more complex functions were riddled with bugs on the first implementation, and the lexical scope handling took about three complete rewrites before I got it right.

If this had gone any further than the three days of off-hours time I spent, I certainly would have rewritten the test suite in Lisp; however it was primarily an academic exercise to really 'get' how Lisps worked and push my comfort level; writing all of my tests in the language I was trying to write would have pushed things a bit to far.

In fact, I never got around to writing a parser, so even if I'd written them in Lisp it would have looked like this:

    var Symbols = require('../Symbols')
    var natives = require('../natives')

    var foo = Symbols.get_symbol_named('foo')
    module.exports = [
        natives.tests,
        [natives.it, [natives.atom, [natives.quote, foo]], true],
        [natives.it, [natives.atom, [natives.quote, []]], true],
    ]