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-protostar-test-adapter

v0.1.6

Published

Run your Protostar tests in the Sidebar of Visual Studio Code

Downloads

4

Readme

⚠️ WARNING! ⚠️

This repo contains highly experimental code. Expect rapid iteration.

🎟️ Description

vscode extension to view protostar tests in the Test Explorer.

This extension uses vscode native Test API

🎗️ Prerequisites

Minimum protostar version required: 0.2.1

Install or upgrade protostar using the command below:

curl -L https://raw.githubusercontent.com/software-mansion/protostar/master/install.sh | bash

For this extension to work properly, you need to create a dedicated profile named ci. This profile should be configured to:

  • have no color on output
  • have a default target to run all tests

Here is an example of the corresponding section in protostar.toml file:

[profile.ci.protostar.shared_command_configs]
no_color=true
cairo_path = ["./lib/cairo_contracts/src"]
target = "contracts"

you can test your setup by running the following command:

protostar -p ci test

📦 Installation

Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.

ext install abuisset.vscode-protostar-test-adapter

🔬 Usage

Click on the Test icon , you should see the list of protostar tests.

test view

Then interact with your tests as any other Test extension.

Test results will be displayed in the test output console.

test view

This extension detects Protostar projects using the protostar.toml file and/or test files like *test*.cairo. If the automatic activation does not work, it is possible to manually launch the extension using the "Launch Protostar Test Explorer" command accessible from the vscode menu (Ctrl-Shift-P).

🫶 Contributing

Contribution guidelines are specified in CONTRIBUTING.md. For contribution ideas, please refer to the contribution page.

Here are the steps for local deployment:

  • install yarn package manager.
  • install the Test Explorer extension
  • fork and clone this repository and open it in VS Code
  • run yarn install
  • run yarn watch or start the watch Task in VS Code
  • start the debugger

You should now see a second VS Code window, the Extension Development Host. Open a folder in this window and click the "Test" icon in the Activity bar. Now you should see your test suite in the side panel:

test view

🌡️ Testing

Unit tests are using jest framework. To run the tests, simply run the following command:

yarn test

To check code coverage, run:

yarn coverage

To check code formatting, run:

yarn lint

You can also format your code by using the following command:

yarn lint:fix

📄 License

Protostar Test Explorer is released under MIT.

❓ Reference