Knapsack Pro

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

TestNG

https://testng.org/doc/documentation-main.html

go test/testing

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

Java

Go

Category

Unit Testing, Intergration Testing, End-to-End Testing

Unit Testing

General info

TestNG is a testing framework for the Java programming language inspired by JUnit and NUnit

TestNG is similar to JUnit and NUnit but with newer functionalities such as: annotations, test that your code is multithread safe, flexible test configuration, support for data-driven testing (with @DataProvider), support for parameters, powerful execution model (no more TestSuite) and more... It's also designed to cover all categories of tests unit, functional, end-to-end, intergration... etc

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
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

However there are Plugins such as https://github.com/tebeka/go2xunitto convert the output of Go testing library into xUnit format
Client-side
Allows testing code execution on the client, such as a web browser

Yes

The scope of testing with testNg is wide and you can test various front-end functionalities and behaviours with it

Yes

Yes it can be used effectively for front-end testing
Server-side
Allows testing the bahovior of a server-side code

Yes

You can test server-side functionalities and behaviours with TestNg

Yes

Yes, it is used by developers for end-to-end testing so the back-end can be tested easily as well
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

Yes

Fixtures are inbuilt into testNG, these are the annotations which are: @BeforeSuite, @AfterSuite, @BeforeTest, @AfterTest, @BeforeGroups, @AfterGroups, @BeforeClass, @AfterClass, @BeforeMethod, @AfterMethod

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
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

You can use various fixtures to setup environments for group tests

Yes

Group fixtures can be done following a similar procedure as a single fixture
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 importing a package called 'gotests' (https://github.com/cweill/gotests)
Licence
Licence type governing the use and redistribution of the software

Apache License 2.0

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 an external library like mockit which intergrates well with testNG

Yes

By use of a third party library GoMock which intergrates well with the testing library
Grouping
Allows organizing tests in groups

Yes

Multiple test cases can be grouped more easily by converting them into testng.xml file, in which you can make priorities which test case should be executed first

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
Other
Other useful information about the testing framework