My strategy for dealing with all these ruby testing fads is to just keep on plugging away with good old Test::Unit and avoid the churn all together. It takes about two minutes to teach somebody how to read asserts and then you're done.
When everybody claiming it's the next big thing decides six months later that it's too cumbersome and complicated and must immediately be replaced with the next shiny new thing. The ruby community seems to suffer from an acute case of magpie syndrome.
Comments
My strategy for dealing with all these ruby testing fads is to just keep on plugging away with good old Test::Unit and avoid the churn all together. It takes about two minutes to teach somebody how to read asserts and then you're done.
" ... all these ruby testing fads "
What makes something a fad or not?
When everybody claiming it's the next big thing decides six months later that it's too cumbersome and complicated and must immediately be replaced with the next shiny new thing. The ruby community seems to suffer from an acute case of magpie syndrome.