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

go test/testing

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

SpecFlow

https://specflow.org/
Programming language

Go

.NET

Category

Unit Testing

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

SpecFlow is a test automation solution for .NET

SpecFlow is a test automation solution for .NET which follows the BDD paradigm, and is part of the Cucumber family. SpecFlow tests are written with Gherkin, using the official Gherkin parser which allows you to write test cases using natural languages and supports over 70 languages.
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

Front-end behaviour is tested. With specflow specifications of the expected behaviours are made and specflow tests against this
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

Back-end behaviour is tested. Specifications of the expected behaviours are made and specflow tests against them
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

BeforeTestRun and AfterTestRun are executed once for each thread which is a limitation of the current architecture.
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)

Yes

SpecFlow contains a generator component. The SpecFlow IDE integration tries to locate the generator component in your project structure, in order to use the generator version matching the SpecFlow runtime in your project
Licence
Licence type governing the use and redistribution of the software

MIT License

BSD 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

Specflow intergrates well with mock to give it excellent mocking capabilities
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 create test suites with specflow
Other
Other useful information about the testing framework