Knapsack Pro

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

go test/testing

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

Jest

https://jestjs.io
Programming language

Go

JavaScript

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

A Unit Testing framework focused on simplicity

This is a Unit test framwork especially designed for the React.JS, Babel, TypeScript, Node, React, Angular and Vue projects. It usually worked with Enzyme(Integration testing)
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

You can easily test methods, properties, UI element actions and other front-end functionalities
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 server behaviour also can be tested with Jest much in the same way as the front-end tests.
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

Fixtures are supported, Jest has many helper functions such as: BeforeEach and afterEach If you have some work you need to do repeatedly for many tests, beforeAll and afterAll if you only need to do setup once, at the beginning of a file.
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

Jest supports 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)

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

Jest uses a custom resolver for imports in your tests making it simple to mock any object outside of your test’s scope. You can use mocked imports with the rich Mock Functions API to spy on function calls with readable test syntax.
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 declare as many test suites as you want. Grouping of tests together is done using a describe block
Other
Other useful information about the testing framework