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

theia-extension-tester

v0.1.4

Published

A testing library built on Selenium to test Eclipse Theia extensions / plugins. Eclipse Che is supported as well.

Downloads

6

Readme

Theia Extension Tester

Theia Extension Tester is a package designed for testing graphical user interfaces of Theia/VS Code extensions integrated to Eclipse Che and other Eclipse Theia based editors.

Writing new user interface tests consists of using page objects which represent specific part of the editor user interface. Page objects are designed to follow VSCode Extension Tester page objects as close as possible. Therefore existing user interface tests for VS Code extensions can be reused fo Eclipse Theia based editors.

Installation process

The fastest way to get started is to install starter package theia-extension-tester through npm or yarn.

npm

To install package with npm execute npm install theia-extension-tester --save-dev.

yarn

To install package using yarn execute yarn add theia-extension-tester --dev.

Selenium WebDriver

The project is using Selenium WebDriver library underneath. The library requires user to download specific Selenium WebDriver from web browser vendor. This step has not been automatized yet so it must be completed manually. Some of the most used Selenium WebDriver can be found in the following table:

| Browser name | Location | |----------------|-----------------------------------------------------------------------| | Chromium | https://chromedriver.chromium.org/ | | Firefox | https://github.com/mozilla/geckodriver/releases | | Microsoft Edge | https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/ |

After downloading and extracting any Selenium WebDriver make it executable by executing chmod 755 <webdriver binary> in command line. The driver does not have to be placed in PATH variable.

Getting started

After successful installation of the package and Selenium WebDriver minor configuration steps are required to be performed which depend on selected editor:

Migration from VSCode Extension Tester limitation

Some features and page objects are not fully compatible in term of user interface with Eclipse Theia based editors. Also some tests may libraries such as fs, child_process and other system specific libraries. It is advised not to use system libraries when testing VS Code extensions to make tests less dependent on system / editor.

Versioning

This project follows Semantic Versioning 2.0.0 but until the project reaches 100% compatibility with VSCode Extension Tester it will stay on 0.y.z and every change should be taken as breaking.