Though writing tests can be cumbersome, it's usually the language culture's own fault. I like to evangelize that tests should be easy to write, easy to read, understand and do maintenance.

That's why I wrote python testing libraries like

* Lettuce - http://lettuce.it, for BDD (Inspired by Cucumber and Ruby)

* Sure - http://falcao.it/sure (Assertion library inspired by should.js)

* HTTPretty - htt[://falcao.it/HTTPretty (For mocking requests)

So lately I have been studying go, making some experiments and loved it so far. But the available testing frameworks and assertion libraries are cumbersome, setup is painful and when you run "go test" there is no colorful output rewarding you for all the hard work you've been doing writing such tests.

That's why I started to prototype a test runner for go, its name is hawkeye:

https://github.com/gabrielfalcao/hawkeye

It uses go's ast, scanner and parser to find specs, put them in a temporary file and run them.

Gophers and hackers who are very experienced with testing, please give some feedback