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

	go test/testing https://golang.org/pkg/testing/	Nose https://nose.readthedocs.io/en/latest/
Programming language	Go	Python
Category	Unit Testing	Unit Testing, unittest Extensions
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	Nose is a Python unit test framework This is a Python unit test framework that intergrates well with doctests, unnittests, and 'no-boilerplate tests', that is tests written from scratch without a specific boilerplate.
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 nose is a unit testing tool which is very similar to unittest. It is basically unittest with extensions therefore just like unittest is can test front-end components and behaviour
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 Nose can test back-end components and functionality as small units. One can write tests for each function that provides back-end functionality
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 nose supports fixtures at the package, module, class, and test case levels, so that initialization which can be expensive is done as infrequently as possible.
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 Group fixtures are allowed with nose, where a multitest state can be defined.
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)	Through use of third party libraries like test-generator and from the 'unittest.TestCase' library
Licence Licence type governing the use and redistribution of the software	MIT License	GNU Library or Lesser General Public License (LGPL) (GNU LGPL)
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 The nose library extends the built-in Python unittest module therefore has access to unittest.mock
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 With nose it collects tests automatically and there’s no need to manually collect test cases into test suites.
Other Other useful information about the testing framework