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

Quick

https://github.com/quick/quick

Behat

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

Swift

PHP

Category

Acceptance Testing, Unit Testing

Functional/Acceptance Testing

General info

Quick is a Swift (and Objective-C) testing framework.

Quick is a behavior-driven development framework for Swift and Objective-C that is inspired by RSpec, Specta, and Ginkgo. Quick comes bundled with Nimble a matcher framework for your tests.

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.

Yes

Yes, it is an xUnit style test framework

No

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

Yes

Developers can test front-end behaviour and components by defining front-end feature specifications

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

Developers can test back-end behaviour and components by defining back-end feature specifications

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

Quick contains fixture methods setup() and teardown() for setting up and destroying test environments

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

Yes, example groups (logical groupings of examples/tests) can share setup and teardown code

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

Yes, developers can create mock objects with Quick using the Cuckoo library

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

Yes

In Quick test suites are named Specs, and every test suite you create starts off with a class inheriting from QuickSpec includes a main method, spec() which contains all the test cases.

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