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

protractor-components

v1.1.8

Published

Simple component builder for protractor

Downloads

3

Readme

protractor-components

Simple component builder for protractor projects

Installing

npm i protractor-components

API

Component

simple class that can get only the common things like getText, getAttribute, getCssValue, etc.

As protractor, all these common types return Promise

Component.prototype.root - root element that find when you call constructor(new keyword).

Collection

Collection like ElementArrayFinder, but you can use for await ... of syntax

Example

// reason.component.ts
import { Component } from 'protractor-components';
import { $ } from 'protractor';

export class Reason extends Component {
    constructor() {
        super($('.row.first .span4'));
    }
    getHeader() {
        return this.$('.text-display-1').getText();
    }

    getBody() {
        return this.$('.text-body').getText();
    }
}


// e2e.ts
import { $ } from 'protractor';
import { Reason } from './reason.component';

describe('...', () =>{
    it('...', async ()=>{
        const reason = new Reason();
        const header = awaitreason.getHeader();
        expect(typeof header).toBe('string';
    })
})

collection example

import { $$ } from 'protractor';
import { Collection } from 'protractor-components';

import { Reason } from './reason.component';

export class ReasonCollection extends Collection<Reason>{
    constructor(){
        super($$('.row.first .span4'), Reason);
    }
}

TODO

  • [x] JSDoc from protractor for Component and Collection
  • [x] more comprehensive types
  • [x] more common components(Form, Selector, MultipleSelector, Checkbox, RadioButton, Input(color picker, range, date, upload) , Table)
  • [x] add module protractor-components/common
  • [] add API for angular(window.ng.probe function) and react(resq library) components