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 🙏

© 2026 – Pkg Stats / Ryan Hefner

as-test

v0.4.4

Published

Testing framework for AssemblyScript. Compatible with WASI or Bindings

Downloads

644

Readme

A lightweight testing framework for AssemblyScript.

🔹 Minimal and fast – Run your tests without unnecessary overhead.

🔹 Familiar API – Inspired by modern JavaScript testing frameworks.

🔹 Powerful mocking – Easily override functions and track calls.

🔹 Seamless CI/CD integration – Works effortlessly in automation pipelines.

🔹 Universal environment – Run your tests on any platform, runtime, or bindings.

💾 Installation

npm install as-test
npm intall json-as

Initialize your test setup with:

as-test init

This creates a test directory at assembly/__tests__/ with a sample test file.

📝 Writing Tests

Create a new test file in assembly/__tests__/, for example, math.spec.ts:

import { describe, test, expect, run } from "as-test";

describe("Math operations", () => {
  test("Addition", () => {
    expect(1 + 2).toBe(3);
  });

  test("Subtraction", () => {
    expect(5 - 2).toBe(3);
  });

  test("Multiplication", () => {
    expect(3 * 3).toBe(9);
  });
});

run();

🔍 Examples

🏗️ Mocking Functions

Use mockFn to override functions during testing:

import { mockFn } from "as-test";

// Mock console.log
mockFn<void>("console.log", (data: string): void => {
    console.log("[MOCKED]: " + data);
});

run();

Or override imported functions with mockImport.

⚒️ Setup and Teardown

Use beforeAll and afterAll to run code before and after a test is run.

import { beforeAll, afterAll } from "as-test";

beforeAll(() => {
  log("Setting up test environment...");
});

afterAll(() => {
  log("Tearing down test environment...");
});

run();

📃 Pretty Logging

Using console.log will mess up the terminal output. Instead, use the inbuilt log function:

import { log } from "as-test";

log("This is a pretty log function");

run();

Or override all existing console.log calls with log:

import { mockFn, log } from "as-test";

mockFn<void>("console.log", (data: string): void => {
    log(data);
});

run();

🔄 Running Tests in CI

To integrate as-test into your CI/CD workflow, see the example configuration.

assembly/__tests__/example.spec.ts

📃 License

This project is distributed under an open source license. You can view the full license using the following link: License

📫 Contact

Please send all issues to GitHub Issues and to converse, please send me an email at [email protected]