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

	go test/testing https://golang.org/pkg/testing/	Suitest https://github.com/SuitestAutomation/suitest-js-api
Programming language	Go	JavaScript
Category	Unit Testing	End-to-End Testing, Browser Automation
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	Suitest is a freemium test automation tool specially designed for Smart/AndroidApple TV, XBOX, PlayStation4 and websites Suitest provides the codeless visual test editor on it's platform to easily create the automation scripts without any knowledge of programming languages. You can also see the version and result history. And Test execution is pretty fast
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 No, Since Suitest has a created custom framework service to test the apps on TV, Gaming consoles and website
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 Suitetest allows for testing front-end components and functionality, it is a browser automation tool after all.
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 Since it performs end-to-end testing this includes critical functionalities like database/server connections, communications and other server-side functionalities
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	N/A
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)	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	Yes Mocks are available
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	You can create suites in suitetest
Other Other useful information about the testing framework