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

	Kiwi https://github.com/kiwi-bdd/Kiwi	Behat https://docs.behat.org/en/latest/
Programming language	Swift	PHP
Category	Unit Testing	Functional/Acceptance Testing
General info	Kiwi is a Behavior Driven Development library for iOS development The goal behind Kiwi is to provide a BDD library that is simple to setup and use, and create tests that are more readable than what is possible with the bundled test framework.	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 Kiwi is an xUnit style framework	No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can test front-end components with kiwi	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 You can test back-end components with kiwi	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 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 kiwi has a beforeEach(aBlock) which is run before every 'it' block in all enclosed contexts. Code that sets up the particular context should go here and afterEach(aBlock) which is run after every it block in all enclosed contexts	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.	Yes through the beforeAll(aBlock) and afterAll(aBlock) functions.	By use of third party libraries like moodle-behat-generators
Licence Licence type governing the use and redistribution of the software	Proprietary, Open source	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 Kiwi has inbuilt support for stubs and mocks,including null mocks, class mocks, protocol mocks	By using third party libraries like Mock and Prophecy
Grouping Allows organizing tests in groups	Yes Kiwi uses the block syntax in iOS to define groups of assertions and share setup state between collections of tests	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