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

vscode-uitests-tooling

v4.1.1

Published

UI tests Utils for Camel Tooling extensions

Downloads

2,042

Readme

Installation

Install vscode-uitests-tooling into your extension devDependencies:

npm install --save-dev vscode-uitests-tooling@latest

Local development

These are necessary steps for local contribution and writing tests with vscode-uitests-tooling package.

Build local changes

  1. Inside vscode-uitests-tooling project execute prepared script, which includes all necessary steps

    npm run dev
  2. Only for the first time - inside project where you are writing tests, you need to link local version of vscode-uitests-tooling package

    npm link vscode-uitests-tooling

Example

Example how to use this library in daily work in some project where you want to write UI tests with usage of vscode-extension-tester testing framework and vscode-uitests-tooling utils package.

  1. Git clone vscode-uitests-tooling on same dir level as your project

    git clone https://github.com/djelinek/vscode-uitests-tooling.git
  2. Inside tests use only import { XYZ } from 'vscode-uitests-tooling' package to import all page-objects including vscode-extension-tester ones

  3. To easily build made utils changes and run tests in one step you can use

    npm --prefix ../vscode-uitests-tooling run dev && npm run ui-test

Migration to 3.0.0

In this version we are trying to simplify whole process of maintaining utils in one place and writing tests in another. To enable this approach we are now re-exporting whole vscode-extension-tester API which means this dependency is not required to be installed in destination where the tests are written because it will be provided as transitive dependency.

It also means that vscode-extension-tester version upgrades can be done only in one place and it will be propagated to all dependant proejcts.

To use vscode-uitests-tooling package in version 3.0.0 you need to change just few easy things and other should stay same.

  1. Remove ExTester devDependency

    npm uninstall vscode-extension-tester
  2. Install UI tests Utils for Camel Tooling package in version 3.0.0

    npm install -D [email protected]
  3. Replace all vscode-extension-tester imports by vscode-uitests-tooling

  4. Run tests!

Contribution

Did you found some bug? Are you missing some feature? Please feel free to open new Issue or Create PR to our GitHub repository.