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

go test/testing

https://golang.org/pkg/testing/

Behat

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

Go

PHP

Category

Unit Testing

Functional/Acceptance 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

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

However there are Plugins such as https://github.com/tebeka/go2xunitto convert the output of Go testing library into xUnit format

No

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

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

Yes, it is used by developers for end-to-end testing so the back-end can be tested easily as well

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

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

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

Group fixtures can be done following a similar procedure as a single fixture

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

They are available by importing a package called 'gotests' (https://github.com/cweill/gotests)

By use of third party libraries like moodle-behat-generators
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

By using third party libraries like Mock and Prophecy
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

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