Peridot vs Ginkgo comparison of testing frameworks
What are the differences between Peridot and Ginkgo?

	Peridot http://peridot-php.github.io/	Ginkgo http://onsi.github.io/ginkgo/
Programming language	PHP	Go
Category	Unit Testing	Unit Testing, Intergration Testing
General info	Peridot is a lightweight, extensible testing framework for PHP It features an event-driven architecture that allows testers to easily customize the framework via plugins and reporters, and uses the 'describe-it', syntax making the testing language clear and readable	BDD testing framework for Go Ginkgo is a BDD testing framework for Go that has a great matcher library to go with it called Gomega and intergrates with the standard testing library
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 Front-end components can be tested with Peridot	Yes Yes, by creating unit tests then testing individual front-end components
Server-side Allows testing the bahovior of a server-side code	Yes Back-end componets and behaviours can be tested as small units	Yes Yes by creating unit tests then testing various back-end components
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Peridot has several methods that allow one to create and define fixtures	N/A
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 There are methods to create group fixtures in Peridot	N/A
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	Yes They are available by running the command: 'ginko bootstrap'
Licence Licence type governing the use and redistribution of the software	MIT License	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)	Peridot does not include mocking out of the box but there are some great tools like 'Mockery' and 'Prophecy' which Peridot intergrates very well with	Yes Dvelopers can generate mocks by using the third party package 'gomock'
Grouping Allows organizing tests in groups	Yes By use of describe and context blocks and it has a Runner which is responsible for running a given Suite.	Yes Ginkgo allows you to group tests in 'Describe' and 'Context' container blocks. It also provides 'It' and 'Specify' blocks to hold your assertions
Other Other useful information about the testing framework