Search code examples
.netunit-testingboo

Is Boo a good choice for writing unit tests?


I'm developing in C# on the Castle stack. I'm new to unit testing, and I've heard that a more flexible language (than C#) might make writing tests easier.

Do you think it is worth the time to learn Boo just for writing unit tests?

We use the SharpDevelop IDE, so have Boo support available, and I've kind of been looking for an excuse to learn a new CLR language, but I just don't want it to get in the way of learning unit testing.


Solution

  • If you're new to unit testing, it might be best to use a familiar language at least until you have the basics under control (maybe a couple of weeks). When you feel that the language/framework that you use is too verbose or restrictive, try something else.

    I'm developing mostly in Java, but I'm planning on moving to Scala. In the future I might still write some parts of the application code in Java, but for the tests I would prefer using Scala, Ruby, Groovy or similar language with a more flexible syntax. For example, with Java/C# you need to use long descriptive method names for the tests, but with a more flexible language you can use just plain strings, which makes the test names much more readable: http://www.codecommit.com/blog/java/the-brilliance-of-bdd