Knapsack Pro

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

Cedar

https://github.com/cedarbdd/cedar

Google Puppeteer

https://developers.google.com/web/tools/puppeteer
Programming language

Swift

JavaScript

Category

Unit Testing

Browser Automation

General info

Cedar is a BDD-style testing for swift using Objective-C

Cedar is a BDD-style Objective-C/Swift testing framework that has an expressive matcher DSL and convenient test doubles (mocks). It provides better organizational facilities than the tools provided by XCTest/OCUnit In environments where C++ is available, it provides powerful built-in matchers, test doubles and fakes

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

Yes

Cedar is an xUnit style framework

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.

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

Yes

You can test back-end components with a bias towards their expected behaviour. Cedar specs also allow you to nest contexts so that it is easier to understand how your object behaves in different scenarios

No

Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

Yes

Cedar has beforeEach and afterEach class methods which Cedar will look for on every class it loads. You can add these onto any class you compile into your specs and Cedar will run them

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

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.

N/A

No

Licence
Licence type governing the use and redistribution of the software

MIT License

Apache License 2.0

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

Cedar contains inbuilt mock/test double functionality

No

Grouping
Allows organizing tests in groups

Yes

Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.

No

Other
Other useful information about the testing framework