8 best alternatives to NW.js (w/xvfb) as of 2019 - Slant

PhantomJS

Top Con

Deprecated by Puppeteer

PhantomJS is no longer actively maintained by the original authors. Puppeteer is said to be a replacement supported and backed by the Google Chrome team, now. See More

Top Pro

Supports screen capture

Top Con

Heavy setup

You'll often end up having PhantomJS binaries connected via WebDriver to your testing framework, possibly using client/server especially if you want your test running with something else than Java. This means an overhead in terms of maintenance and performance, but still usually lighter than running a full browser (like Chrome, Firefox, IE). See More

Top Pro

Used in many open source projects

Including bootstrap, grunt, ember.js, and YUI. See More

Top Con

Browser closes unexpectedly

It often happens when running on more then 5 (my measurement) JVM instances that the browser gets stuck and quits unexpectedly. This can be partially solved by running the instances one by one instead of parallel (this is a problem when testing Jenkins and Bamboo agents) but I don't believe this qualifies as a solution. The error is called UnreachableBrowserException. See More

Top Pro

Supports many browser standards

PhantomJS has full DOM and CSS parsing, JSON, canvas, and SVG support. See More

Top Con

Elements are sometimes not visible

This is an error which occurs with almost no reason, PhantomJS sometimes decides that it cannot click the element even though the element is intractable or enabled. This happens if you have to scroll to see the element (and these are not pages that load elements with JavaScript) which is strange because PhantomJS should catch the whole page if it is not loaded explicitly with JavaScript. This problem partially goes away with re-sizing the browser, but that does not really qualify as a solution. The error it raises is: ElementNotVisibleException. See More

Top Pro

Built on WebKit

WebKit is becoming the gold standard for browser compatibility, making it a good starting point for native headless browser testing. See More

See All Experiences

27 2

Zombie.js

Top Pro

Runs on Node.js

Zombie is built on node.js, making it very easy to integrate with your project and into your testing toolchain. It only requires JavaScript to run. See More

Top Con

Support has waned

As of August 19, 2016, Zombie hasn't received a commit since January 2016. Issues get comments like "patch welcome". See More

Top Pro

Fully featured api based interaction and assertion

The way the api is built makes it very easy to add to your test framework. See More

Top Con

Stale documentation

Full API documentation has been missing since the start, making it frustrating to use. See More

Top Pro

Claims to be "Insanely Fast"

It's a lot faster than fully fletched browsers and a lot lighter. Partly because it really only focuses on headless loading of pages along with their JavaScript (not taking really care of rendering or more visual resources). See More

Top Con

Fails to load many sites

As its JavaScript and DOM engine are mostly "just good enough" and because by design it'll report all errors and stop there, many complex sites will not load properly through Zombie.js. See More

Top Con

No screen-shot

As it doesn't render the page, you cannot get a screenshot to for testing or reporting test failures. See More

See All Experiences

7 2

React Native

Top Pro

Allows you to develop native apps

React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper. See More

Top Con

Steep learning curve

React Native is not the most beginner-friendly framework for creating mobile apps with JavaScript. It requires that the developer know React, which is known to have a steep learning curve. See More

Top Pro

Backed by Facebook

Facebook writes their mobile apps in React Native so the code base gets pretty thoroughly used in some highly demanding scenarios. See More

Top Con

If core team doesn't use a certain feature, it's not developed

Whenever there's functionality you need that they don't use in their apps, it's not going to get developed by them, even if it's obvious it should be in the core. They always say to either submit a PR or create a separate module. See More

Top Pro

Large, supportive community

Despite being such a young framework (early 2015), the support for React Native grew quickly. There is a forum, active tag on Stackoverflow and many other ways to get help from the community. See More

Top Pro

More predictable control of the state

The one way data flow, makes it more predictable and easy to control. See More

77 22

Electron

Top Con

Needs to run chromium

Runs chromium in the background which consumes a lot of resources. See More

Top Pro

Active development

Electron receives updates frequently (multiple times each month). For example, the recent updates (as of July 15, 2016) are: 1.2.6 (released July 6) 1.2.5 (released June 23) 1.2.4 (released June 22) 1.2.3 (released June 16) 1.2.2 (released June 8) See More

Top Con

Apps can have memory issues

Apps made with Electron are likely to have memory issues unless you specifically design the app with efficient coding. See More

Top Pro

Healthy community

Github is behind electron and there is a lot of big companies using it to make their cross platform apps. See More

Top Pro

Great documentation

Electron has a nice website with great documentation. It also features a lot of samples. See More

Top Pro

Solid API

20 11

Help millions of people make better decisions.

Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.