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

screen.object

v1.1.2

Published

Page Object Pattern for Appium and Mocha.

Downloads

4

Readme

screen.object

Dependency Status NPM version

Page Object Pattern for Appium and Mocha.

Configuration

It can be a bit complicated to explain, so please take a look at the example (todo) to have a better idea of how to set everything up.

  • Add a file called drivers.settings.js to your project root and configure it based on this example:
module.exports = {
  screensDir      : 'test/screen',        // DEFAULT
  remote          : ['localhost', 4723 ], // DEFAULT

  // REQUIRED!
  capabilities    : {
    ios           : {
      device      : 'iPhone Simulator',
      app         : require('path').resolve(__dirname, 'build', 'my.app')
    }
  }
};
  • Create a directory to hold your screen objects under test/screen.
  • Require screen.object in your mocha options. If you are using mocha.opts you can just add --require screen.object to it.
  • Write your Mocha describes as the following example and you'll have the screens required from your screen directory.
describe('Home', withScreen('HomeScreen', function(screen) {
  ...
}));

Running the Appium server automatically

If you want screen.object to run the Appium server automatically, you can --require screen.object/appium in your mocha options. And just like mocha.opts you can specify a appium.opts under your test directory with the options you want your server to start with.

License

This is licensed under the feel-free-to-do-whatever-you-want-to-do license.