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

@pumpo5.dev/core

v0.0.84

Published

The Pumpo5 client to be used with a Selenoid test farm

Downloads

809

Readme

Pumpo no.5 for Playwright

This is a package for running Playwright tests in a Selenoid test farm.

It will start an instance of Chrome in a test farm for each test case, send commands using the Chrome DevTools Protocol, and close the session in the end.

At the moment only Chrome browser is supported. Firefox and Webkit (Safari) browsers are not supported.

Getting Started

Assuming that you already have one or more Playwright test suites ready in your system, all you need to do is:

  • Install this package in your project.
  • Import the test and expect functions from the '@pumpo5.dev/core' package

Installation

Install this package in your project which includes the Playwright tests:

$ npm install --save-dev @pumpo5.dev/core

Or if you prefer Yarn:

$ yarn add --dev @pumpo5.dev/core

Import the functions in your tests:

...

import { test, expect } from '@pumpo5.dev/core'

...

And just write your tests using the test and expect functions like you usually do.

Usage

In order connect to a test farm, you need to create a configuration file. This file must be named config.conf.

Before any tests are executed, the package will load and look for this file in three ways:

  • First, it will check if an environment variable named CONFIG_PATH is set.

    If it is, it will then check its value and verify if it is a path that points to a file named config.conf.

    In case positive, it will then try to load the configuration by reading this file.

  • Second, if no CONFIG_PATH environment variable is set, the package will check if a command line argument was passed to NodeJS contaning a path to any file named config.conf. In case positive, it will then try to load the configuration by reading the file pointed by this command line argument.

  • Third and last, in case the other methods failed, the reporter will look for a config.conf file in the project's root folder and directories above.

    In case it finds a config.conf in any of those directories it will proceed to load it and use it to set its internal configuration.

The keys that could or should be included in this configuration file are as follows:

Key | Type | Mandatory | Description ---|--------|---|--- webdriverUrl | String | Yes | The URL where the test farm is running. For example, if you have it running in your localhost, it could be http://localhost:4444 chromeOptions | Object | No | The initialization options for the Chrome browser, passed as desired capabilities (e.g. goog:chromeOptions. Must be contained in one line. For example chromeOptions={"args": ["--start-fullscreen"]})

Other versions

If you like this project, please check Pumpo#5 in Java as well, here and here :)

Authors

License

Apache License 2.0 © PumpITup