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

testcafe-browser-provider-idevice

v0.0.188

Published

idevice TestCafe browser provider plugin.

Downloads

10

Readme

testcafe-browser-provider-idevice

Build Status

This is the idevice browser provider plugin for TestCafe.

Install

npm install testcafe-browser-provider-idevice

Usage

You can determine the available browser aliases by running

testcafe -b idevice

When you run tests from the command line, use the alias when specifying browsers:

testcafe idevice:browser1 'path/to/test/file.js'

A 'browser' is the device you'd like to test in this case. For simulators use "simulator.{simulator Name}"

eg testcafe 'idevice:simulator.iphone 8' 'path/to/test/file.js'

You can find your simulators using

xcrun simctl list

When you run on a real device, you require a few steps.

  1. Install XCode
  2. Open the XCUITest testApplication.
  3. Select your team (Personal is fine). Make sure you do both targets (There's a little dropdown)
  4. Run the app
  5. Run the test in XCode. Note that the test will fail if you have a code to lock your phone. Remove it, and set your phone to stay unlocked forever. Its a test device.
  6. Run your tests. Make sure the testcafe server (your mac) and the device are accessible and on the same network as each other. If you can't connect then the browser will open, but nothing will load.

Real devices are configured with their UUID as the device name, for example:

testcafe 'idevice:f655a41e4fe4c7db93571fb143f91a5a4a7c1e34' test.js

When you use API, pass the alias to the browsers() method:

testCafe
    .createRunner()
    .src('path/to/test/file.js')
    .browsers('idevice:browser1')
    .run();

Author

Bradley Smith (https://bradleysmith.dev)