Spock vs easyb

Question

I just looked briefly at easyb and spock, both seem similar, however spock seems to be more technically oriented, is there any better practice as to when to use that?

For example, which one should be used for a new Grails project? which one should prefer for a java project for old projects, for which you just need to write automated tests? one more suitable for integration tests than the other?

Things of that kind.

Thanks Sudarshan

Answer 1

Spock vs EasyB Spock is a BDD-based framework that provides developers with tools to make their lives easier. EasyB is a great way to capture requirements and create acceptance tests. EasyB scripts can be short stories and can be left blank to make them descriptive stories. Then start adding the closing code and you can enter selenium, etc. ( source )

While browsing the web, I saw opinions that EasyB has some usability issues that are still puzzled. Moreover, I managed to find many more articles, textbooks, etc. On Spock than EasyB, which seems to be less popular.

Spock is based on JUnit, so running test cases for regular Java projects is as easy as running any regular JUnit tests, whether from IDEs or continuous integration servers. See Testing with Spock .

In conclusion, I would stick with Spock.