Google Puppeteer vs microtest comparison of testing frameworks
What are the differences between Google Puppeteer and microtest?

	Google Puppeteer https://developers.google.com/web/tools/puppeteer	microtest https://github.com/rubyworks/microtest
Programming language	JavaScript	Ruby
Category	Browser Automation
General info	Puppeteer is a Node library which provides browser automation for chrome and chromium Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium; It provides a high-level API to control Chromium or Chrome over the DevTools Protocol	Minimal testing framework, compatible with Test::Unit/MiniTest
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No
Client-side Allows testing code execution on the client, such as a web browser	Yes Most things you can do manually in the browser can be done using puppeteer, therefore you can create a testing environment for your tests to run directly. You can test front-end functionality such as UI testing with puppeteer
Server-side Allows testing the bahovior of a server-side code	No
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	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.	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.	No
Licence Licence type governing the use and redistribution of the software	Apache License 2.0	FreeBSD 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)	No
Grouping Allows organizing tests in groups	No
Other Other useful information about the testing framework