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

polymer-tests-generator

v1.1.0

Published

CLI for generating tests for Polymer components

Downloads

3

Readme

polymer-tests-generator

Automate your Polymer components tests creation

What the heck is this?

Aren't your tired of manually creating tests folders/files for Polymer components? I am. And maybe, like me, you are not using polymer-cli to generate every new shiny component.

And here comes polymer-tests-generator, simple cli intended to automate this process. 🎉🎉🎉

Installation

npm install -g polymer-tests-generator

yarn global add polymer-tests-generator

Usage

polymer-tests [options]

CLI options

-p, --path - specifies path in which tests generation will occur

Okay, but how it works ❓

Let's say you have structure like this:

--siema
  --demo
    -demo.html
  --elo
    -elo.1.html
    -elo2.html
  -elo.html
  -siema.html

Generator will search this structure looking for components. It will exclude everything from your .gitignore file and demo folder.

When it's done searching it start the magic using seed files and recursive search✨✨✨

First it checks for test folder and creates it if needed. Then does the same for test/index.html file. And lastly it creates tests only if they don't exist for given component.

So if you already have a test for siema.html it's not gonna override it.

That's it. Simple and fun when machine does it for you!

Seed files

Contributions

Feel free to create issues and pull request. But please, for any new feature first create an issue so we can discuss it :)

Todo

  • [ ] update suites list in index.html
  • [ ] improve checking if test exists
  • [ ] generate tests for mixins