Blue Ocean vs Testling: What are the differences?

What is Blue Ocean? A reboot of the Jenkins CI/CD User Experience. Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team.

What is Testling? Automatic browser tests on every push. Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.

Blue Ocean and Testling can be categorized as "Continuous Integration" tools.

Some of the features offered by Blue Ocean are:

• Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
• Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
• Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.

On the other hand, Testling provides the following key features:

• Write tests with a minimal test api that works in both node and browsers.
• Run your tests in node and your local browsers.
• Run tests in mocha for qunit, tdd, bdd, and exports-style tests.

Blue Ocean and Testling are both open source tools. It seems that Blue Ocean with 2.49K GitHub stars and 435 forks on GitHub has more adoption than Testling with 337 GitHub stars and 47 GitHub forks.