chromedp - Package chromedp is a faster, simpler way to drive browsers (Chrome, Edge, Safari, Android, etc) without external dependencies (ie, Selenium, PhantomJS, etc) using the Chrome Debugging Protocol

  •        321

Package chromedp is a faster, simpler way to drive browsers in Go using the Chrome Debugging Protocol (for Chrome, Edge, Safari, etc) without external dependencies (ie, Selenium, PhantomJS, etc).NOTE: chromedp's API is currently unstable, and may change at a moments notice. There are likely extremely bad bugs lurking in this code. CAVEAT USER.

https://github.com/knq/chromedp

Tags
Implementation
License
Platform

   




Related Projects

chromedp - A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol.

  •    Go

Package chromedp is a faster, simpler way to drive browsers supporting the Chrome DevTools Protocol in Go using the without external dependencies (ie, Selenium, PhantomJS, etc). Please see the examples project for more examples. Please refer to the GoDoc API listing for a summary of the API and Actions.

serverless-chrome - 🌐 Run headless Chrome/Chromium on AWS Lambda (maybe Azure, & GCP later)

  •    Javascript

Serverless Chrome contains everything you need to get started running headless Chrome on AWS Lambda (possibly Azure and GCP Functions soon). Why? Because it's neat. It also opens up interesting possibilities for using the Chrome DevTools Protocol (and tools like Chromeless or Puppeteer) in serverless architectures and doing testing/CI, web-scraping, pre-rendering, etc.

chrome-remote-interface - Chrome Debugging Protocol interface for Node.js

  •    Javascript

Chrome Debugging Protocol interface that helps to instrument Chrome (or any other suitable implementation) by providing a simple abstraction of commands and notifications using a straightforward JavaScript API. This module is one of the many third-party protocol clients.

cuprite - Headless Chrome driver for Capybara

  •    Ruby

Cuprite is a pure Ruby driver (read as no Java/Selenium/WebDriver/ChromeDriver requirement) for Capybara. It allows you to run your Capybara tests on a headless Chrome or Chromium by CDP protocol. Under the hood it uses Ferrum which is high-level API to the browser again by CDP protocol. The emphasis was made on raw CDP protocol because Headless Chrome allows you to do so many things that are barely supported by WebDriver because it should have consistent design with other browsers. The design of the driver will be as close to Poltergeist as possible though it's not a goal.

remotedebug-ios-webkit-adapter - Debug Safari and WebViews on iOS from tools like VS Code, Chrome DevTools, Mozilla Debugger

  •    TypeScript

RemoteDebug iOS WebKit Adapter is an protocol adapter that Safari and WebViews on iOS to be debugged from tools like VS Code, Chrome DevTools, Mozilla Debugger.html and other tools compatible with the Chrome Debugging Protocol. Before you use this adapter you need to make sure you have the latest version of iTunes installed, as we need a few libraries provided by iTunes to talk to the iOS devices.


Splinter - Python test framework for web applications

  •    Python

Splinter is an open source tool for testing web applications using Python. It lets you automate browser actions, such as visiting URLs and interacting with their items. Splinter is an abstraction layer on top of existing browser automation tools such as Selenium, PhantomJS and zope.testbrowser. It has a high-level API that makes it easy to write automated tests of web applications. It has drivers for Chrome and Firefox for browser-based testing, and zope.testbrowser and PhantomJS for headless testing.

puppeteer - Headless Chrome Node API

  •    Javascript

Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome or Chromium. Note: When you install Puppeteer, it downloads a recent version of Chromium (~170Mb Mac, ~282Mb Linux, ~280Mb Win) that is guaranteed to work with the API. To skip the download, see Environment variables.

mochify.js - β˜•οΈ TDD with Browserify, Mocha, Headless Chrome and WebDriver

  •    Javascript

Browserifies ./test/*.js, decorated with a Mocha test runner, runs it in Headless Chrome and passes the output back to your console. Cleans up your stack traces by mapping back to the original sources and removing lines from the test framework.For proxy settings and other environment variables, see the Puppeteer documentation.

chrome-har-capturer - Capture HAR files from a headless Chrome instance

  •    Javascript

Capture HAR files from a headless Chrome instance. Under the hood this module uses chrome-remote-interface to instrument Chrome.

headless-devtools - Lets you perform Chrome DevTools actions from code by leveraging Headless Chrome+Puppeteer

  •    Javascript

Lets you perform Chrome DevTools actions from code by leveraging Headless Chrome+Puppeteer. Chrome DevTools is great for getting valuable information about your app πŸ•΅οΈ‍♂️. Using headless-devtools you can automate this process πŸ€–. One use-case is to collect this data over time πŸ“ˆ, which can help you keep your app in good health πŸ‘©‍βš•οΈ.

debugger-protocol-viewer - DevTools Protocol API docs—its domains, methods, and events

  •    HTML

Explore the Chrome DevTools Protocol, its methods, events and basic documentation. We deploy to https://chromedevtools.github.io/devtools-protocol/ despite the source living here. The repo/branch layout is described here. Master branch of this repo is deployed every hour (on the 15 minute mark) via the devtools-protocol/scripts/update-n-publish-docs.sh script.

chromeless - πŸ–₯ Chrome automation made simple. Runs locally or headless on AWS Lambda.

  •    TypeScript

You can try out Chromeless and explore the API in the browser-based demo playground (source).With Chromeless you can control Chrome (open website, click elements, fill out forms...) using an elegant API. This is useful for integration tests or any other scenario where you'd need to script a real browser.

chromeless - πŸ–₯ Chrome automation made simple. Runs locally or headless on AWS Lambda.

  •    TypeScript

You can try out Chromeless and explore the API in the browser-based demo playground (source). With Chromeless you can control Chrome (open website, click elements, fill out forms...) using an elegant API. This is useful for integration tests or any other scenario where you'd need to script a real browser.

hihat - :tophat: local Node/Browser development with Chrome DevTools

  •    Javascript

Runs a source file in a Chrome DevTools process. Saving the file will reload the tab.This is useful for locally unit testing browser code with the full range of Web APIs (WebGL, WebAudio, etc). It provides access to profiling, debugger statements, network requests, and so forth.

taiko - A node.js library to automate chrome/chromium browser

  •    Javascript

Taiko is a free and open source browser automation tool built by the team behind Gauge from ThoughtWorks. Taiko is a node library with a clear and concise API to automate the chrome browser. Tests written in Taiko are highly readable and maintainable. Taiko’s smart selectors make tests reliable by adapting to changes in the structure of your web application. With Taiko there’s no need for id/css/xpath selectors or adding explicit waits (for XHR requests) in test scripts.

chrome-headless-screenshots - Using headless Chrome as an automated screenshot tool (alternative to PhantomJS)

  •    Javascript

May 2018 The Chrome team has released Puppeteer, which makes much of the code in this repository obsolete. As such, this project is no longer maintained and issues have been disabled. Please check out Puppeteer. This repo contains an example implementation of using headless Chrome as an automated screenshot tool on linux, which is a common use case for PhantomJS. Contributions are welcome.

awesome-chrome-devtools - Awesome tooling and resources in the Chrome DevTools & DevTools Protocol ecosystem

  •    Javascript

Awesome tooling and resources in the Chrome DevTools & DevTools Protocol ecosystem

sinon-chrome - Testing chrome extensions with Node.js

  •    Javascript

Sinon-chrome is helper tool for unit-testing chromium and Firefox extensions and apps. It mocks all extensions api with sinon stubs that allows you to run tests in Node.js without actual browser. API mocks are generated using official chromium extensions API (Firefox webextensions) schemas that ensures consistency with real API. Actual schemas are taken from Chrome 53 and Firefox 49.

mocha-phantomjs - :coffee: :ghost: Run client-side mocha tests in the command line through phantomjs

  •    Javascript

Ariya Hidayat archived phantomjs on March 3rd, 2018. (See this tweet for more info). phantomjs served us all as great headless browser for years, but now with Electron and headless modes for both Chrome and Firefox, we have much better options. mocha-chrome is a project inspired by mocha-phantomjs, so migration should be easy, and you will be running your tests on the same browser that 50% of your users actually use! I highly recommend it. I will accept pull requests still, but I won't be answering issues or doing feature work myself.