Back to unit tests

One thing that it doesn't seem easy with the easyB+groovy combination is getting a precise indication of what gone wrong. You can get a succesful build with a NPE in a scenario, and the resulting stacktrace is not very informative.

So, we're back to unit testing to check basic functionality before passing the classes to behaviour testing.

The commit I just made has a new unit test, that unfortunately doesn't pass. I'll work on it later.

Comments

Popular posts from this blog

EasyB story fixed

Eclipse + Groovy + EasyB + Maven...

Still no clues...