npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

elm-webdriver

v3.0.3

Published

Elm bridge for Webdriver.io and testing utilities

Downloads

20

Readme

Elm Webdriver

Remote control a browser with selenium, in Elm!

This can be used as a testing suite or you can utilize the exposed API for adapting it to your own use case.

asciicast

Quick Start

Since this package contains a Native module (some javascript), this cannot be published in packages.elm-lang.org. Instead, you need to install it using npm. Do this at the root of your Elm project, where the elm-package.json file is:

npm install elm-webdriver

You are now ready to copy some skeleton tests into your project folder. The the files from the templates folder and copy them to your tests folder in your project.

Edit Main.elm so it looks similar to the example file

If you need to use modules from your project, make sure you also add all the dependencies from the main elm-package.json into webdriver-tests/elm-package.json. Remember to keep those in sync.

Install selenium webdriver

To run tests locally you need the Selenium standalone server.
Download the .jar file from the official Selenium page and run it like this:

java -jar selenium-server-standalone.jar

You are now ready to run your tests. In another terminal, while the standalone server is still running:

cd webdriver-tests
../node_modules/.bin/elm-webdriver

You can also filter tests by name:

../node_modules/.bin/elm-webdriver --filter "Some Test Name"

If the Selenium server complains:

WARN - Exception: The path to the driver executable must be set by the webdriver.gecko.driver system property; 
for more information, see https://github.com/mozilla/geckodriver. 
The latest version can be downloaded from https: //github.com/mozilla/geckodriver/releases                  

Make sure you have the geckodriver installed, and tell Selenium where it is by setting the system property:

java -Dwebdriver.gecko.driver="<path-to-geckodriver>" -jar selenium-server-standalone.jar

API

Check the API Docs