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

@awam/ti.appium

v0.1.1

Published

Plugin for using appium as part of the Titanium build process

Downloads

5

Readme

ti.appium

NPM Version NPM Downloads

Warning this project is purely for investigatory purposes in my own time, so please do not expect any advanced support other than being pointed to examples. However, if you do use it, awesome! :)

This is a Titanium CLI hook, that abstracts away the need for managing appium, webdriver bindings etc (all the horrible bits) when doing UI automation. All you need to worry about is deciding your webdriver package, and writing your tests.

  • If you can think of any features that you'd like, file an issue. But there are no guarantees it would be implemented.
  • If you find bugs, please file an issue, with as much information as you can.
  • If you'd like to contribute, message me on ti-slack.

Usage

Getting started

To get started:

  1. Install the package using [sudo] npm install -g @awam/ti.appium
    • This will install the package for use
  2. Run tiappium-init-hook
    • This will add the CLI hook into your Titanium config
  3. Run tiappium-init-project(In a Titanium project root)
    • This will copy across a basic template into your project.

Writing tests

  • You can choose from two webdriver implementations wd, and webdriverio. You can specify which one to use in the main config file at e2e/config.json, by setting the driver property to either wd or webdriverio
  • There are currently two examples for the (standard Titanium template)[https://github.com/ewanharris/appium-test-repo] and KitchenSink-v2

Running the tests

  • Building with the --appium flag with make the tests run at the end of the build process, under the hood this will add the --build-only flag for you as we need to hand off the app to appium for installation.
  • You will need to setup the desired targets for the platform in the platform specific config at e2e/<platform>/config.json, this will eventually become a CLI option too.
  • It's not pretty, but yes you do need to run the build every time. Eventually I foresee a command that is solely designed to run the tests when you're just writing tests and not actually making edits to your app.

Resources

Appium site - Look here for getting started tips, you do not need to install appium itself as it is contained in this package. appium-doctor - Check if you're actually set up for doing this wd - One of the possible binding choices webdriverio - The other binding choice

Possible plans

This is just a brain dump of stuff that I'd like to try and implement, it should probably become GitHub issues.

  • ti appium command that will only run the tests with the existing app.
  • Maybe move the webdriver/appium packages out of the dependencies and into peerDependencies/the app
    • It takes forever to install this package (added 1809 packages in 360.666s....)
    • It's all overridable anyway