Test-Driven Development

Last month, Rob did a talk about test-driven development at SLUG. It made me wonder: Does God employ test-driven development… and are we the product, or the test-suite?

This entry was posted in General. Bookmark the permalink.

9 Responses to Test-Driven Development

  1. tuppa says:

    What’s more worrying is…. we *ARE* code?

  2. We are quite obviously the test-suite, I’m afraid…

  3. Jussi Kukkonen says:

    I’m thinking we’re just a mock-up. You know, something that the consultants are showing God:
    “So, this is the feeling we’re going for, what do you think?… Oh that, that’s Rwanda, just a small glitch — it’s already fixed in the trunk.
    Don’t touch that! Outer space is not implemented yet, we’re having some problems with the infiniteness you requested: it’s bigger than we assumed.”

  4. We’re all those bits in the test suite that are prefixed by

    # this should never happen, but test it anyway

  5. TonyWeston says:

    We’re defiantly the Test-suite!!…..Millions of little instances of Human(), all with slight variations, all running in a test environment……Should one fail a test (say, by falling off a cliff), then that instance is immediately terminated, the erroneous code discarded, and eventually the storage occupied by the instance is GC’d back to the land. If not run in test mode, then the whole of reality would crash with a ‘unexpectedTerminationException’, every time someone did something dumb.

  6. Rog says:

    He/she/it doesn’t employ TDD, we are the bugs. ๐Ÿ™‚

  7. Andrew says:

    I suppose that is the advantage of being infallible?

  8. Drew says:

    The Bible is quite clear about this in several places including Philippians 1:6:

    “And I am sure of this, that he who began a good work in you will bring it to completion at the day of Jesus Christ.”

    (http://www.gnpcb.org/esv/search/?q=philippians+1:6 – it’s like the Google of online Bibles. APIs and everything ๐Ÿ™‚

  9. Johan says:

    I think the following would be a fitting exit:

    The following error was encountered: The operation completed successfully.

Comments are closed.