Spock vs Behat comparison of testing frameworks
What are the differences between Spock and Behat?

Spock

http://spockframework.org/

Behat

https://docs.behat.org/en/latest/
Programming language

Java

PHP

Category

Unit Testing

Functional/Acceptance Testing

General info

Spock is a testing and specification framework for Java and Groovy applications

Spock has a highly expressive specification language, and due to its JUnit runner, Spock is compatible with most IDEs, build tools, and continuous integration servers.Spock is inspired from JUnit, RSpec, jMock, Mockito, Groovy, Scala, Vulcans among others

Behat is an open source Behavior-Driven Development framework for PHP.

Behat uses the StoryBDD subtype of behaviour-driven development (the other subtype is SpecBDD); This means the tests we write with Behat look rather like stories than code. It is inspired by Ruby's Cucumber
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Spock tests front-end components and functionality by unit testing individual classes and functions

Yes

To enable Behat to test a website, you need to add Mink and a browser emulator (selenium maybe, though slow) to the mix. Mink methods are the connector between Behat and an extensive list of available drivers, and they provide a consistent testing API.
Server-side
Allows testing the bahovior of a server-side code

Yes

Spock tests back-end components and functionality by unit testing individual classes and functions

Yes

Behat can be used for Data Integrity Testing to verify that database operations are functioning properly
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

Yes

Spock contains four methods for setting up environments :setup() (run before every feature method), cleanup() (run after every feature method), setupSpec() (run before the first feature method), cleanupSpec() (run after the last feature method)

Yes

One can use the 'Doctrinefixturesbundle' to create the required fixture loaders and load them in our Behat scenarios when required, using the 'BeforeScenario' hook.
Group fixtures
Allows defining a fixed, specific states of data for a group of tests (group-fixtures). This ensures specific environment for a given group of tests.

Yes

You can use the fixture methods to setup environments for groups of tests.

Yes

Behat allows for group fixtures
Generators
Supports data generators for tests. Data generators generate input data for test. The test is then run for each input data produced in this way.

N/A

By use of third party libraries like moodle-behat-generators
Licence
Licence type governing the use and redistribution of the software

Apache License 2.0

MIT License

Mocks
Mocks are objects that simulate the behavior of real objects. Using mocks allows testing some part of the code in isolation (with other parts mocked when needed)

Yes

Spock has inbuilt mocking capabilities and has no need for external libraries

By using third party libraries like Mock and Prophecy
Grouping
Allows organizing tests in groups

Yes

You can create suites manually in spock

Yes

You can use tags to group features and scenarios together, independent of your file and directory structure
Other
Other useful information about the testing framework