go test/testing vs Cedar comparison of testing frameworks
What are the differences between go test/testing and Cedar?

	go test/testing https://golang.org/pkg/testing/	Cedar https://github.com/cedarbdd/cedar
Programming language	Go	Swift
Category	Unit Testing	Unit Testing
General info	go test is an inbuilt tool/command for conducting automated tests in Golang while testing is the inbuilt testing library Testing is the package that is shipped with go and combines with the go test command to provide a minimal but complete testing experience	Cedar is a BDD-style testing for swift using Objective-C Cedar is a BDD-style Objective-C/Swift testing framework that has an expressive matcher DSL and convenient test doubles (mocks). It provides better organizational facilities than the tools provided by XCTest/OCUnit In environments where C++ is available, it provides powerful built-in matchers, test doubles and fakes
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No However there are Plugins such as https://github.com/tebeka/go2xunitto convert the output of Go testing library into xUnit format	Yes Cedar is an xUnit style framework
Client-side Allows testing code execution on the client, such as a web browser	Yes Yes it can be used effectively for front-end testing	Yes You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.
Server-side Allows testing the bahovior of a server-side code	Yes Yes, it is used by developers for end-to-end testing so the back-end can be tested easily as well	Yes You can test back-end components with a bias towards their expected behaviour. Cedar specs also allow you to nest contexts so that it is easier to understand how your object behaves in different scenarios
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Yes it's straightforward in that first when you run 'go test' for packages in the scope the test will be executed with its working directory set to the source directory of the package being tested. Second the 'go test' tool will ignore any directory in your $GOPATH that starts with the word 'testdata' , starts with a period or an underscore	Yes Cedar has beforeEach and afterEach class methods which Cedar will look for on every class it loads. You can add these onto any class you compile into your specs and Cedar will run them
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 Group fixtures can be done following a similar procedure as a single fixture	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.	Yes They are available by importing a package called 'gotests' (https://github.com/cweill/gotests)	N/A
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)	Yes By use of a third party library GoMock which intergrates well with the testing library	Yes Cedar contains inbuilt mock/test double functionality
Grouping Allows organizing tests in groups	Yes The short answer is yes, by use of table tests which are a great way of performing multiple I/O tests on a function or behaviour with minimal code	Yes Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.
Other Other useful information about the testing framework