[TIP] running away from RSpec

Gary Bernhardt gary.bernhardt at gmail.com
Sat Feb 12 21:22:27 PST 2011

On Sat, Feb 12, 2011 at 1:26 PM, Alfredo Deza <alfredodeza at gmail.com> wrote:
> It is *very* difficult to talk about things that exist in other languages
> that are great
> and that they do not exist in Python.
> It is also not a case of "if you like it so much just use BLEH". I just
> think we can
> come up with different and better things and should be talking about that
> too.

Sounds awesome. Sadly, I don't have any original ideas for test runners.

As an interesting data point, here's how RSpec started:

Initially BDD was just a discussion among Aslak Hellesoy and Dan North
in the ThoughtWorks London office. Dave Astels joined the conversation
with a blog post stating that he thought these ideas could be easily
implemented in Smalltalk or Ruby. Steven Baker jumped in with an
initial implementation, and released RSpec 0.1.
""" [1]

That was in 2005 (!)

Clearly, RSpec wasn't conceived because of Ruby. Ruby just happens to
be a versatile substrate that can accommodate novel tools. The hard
part is coming up with a novel way to write tests, and that seems to
happen rarely.

[1] http://blog.nicksieger.com/articles/2007/11/04/rubyconf-day-3-behaviour-driven-development-with-rspec


More information about the testing-in-python mailing list