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

tinnytest

v0.0.18

Published

A package to run the test script for Lit Protocol with custom commands

Downloads

143

Readme

Tinny

Tinny is a mini test framework, serving as a temporary solution for running e2e tests in TypeScript until we can integrate Jest. It utilizes esbuild for its rapid compilation speed to bundle all the tests into a single test.mjs file, then runs the built test.mjs file immediately. See Benchmark

Prerequisite

  • Node v20 or above
  • The generated file networkContext.ts after running npm run deploy -- --network custom in the lit-assets repo

How to run

In most cases, you will only need the following two environment variables, and a --filter flag. See API

The testName specified in the filter must be the same as the function name.

to run all tests

// run all tests on local chain
DEBUG=true NETWORK=custom yarn test:local

// run filtered tests on datil-test
DEBUG=true NETWORK=datil-test yarn test:local --filter=testExample
DEBUG=true NETWORK=datil-test yarn test:local --filter=testExample,testBundleSpeed

// run filtered tests by keyword
DEBUG=true NETWORK=datil-test yarn test:local --filter=Encrypt

// eg.
yarn test:local --filter=testExample,testBundleSpeed

API

Below is the API documentation for the ProcessEnvs interface, detailing the configurable environment variables and their purposes:

NOTE: a .env.sample is contained in the repository root for the below env tables

| Variable | Description | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | MAX_ATTEMPTS | Each test is executed in a loop with a maximum number of attempts specified by devEnv.processEnvs.MAX_ATTEMPTS. | | TEST_TIMEOUT | The maximum number of milliseconds to wait for a test to complete. | | NETWORK | The network to use for testing, which can be one of the following: LIT_NETWORK.Custom, LIT_NETWORK.DatilDev, or LIT_NETWORK.Datil. | | DEBUG | Specifies whether to enable debug mode. | | REQUEST_PER_KILOSECOND | To execute a transaction with Lit, you must reserve capacity on the network using Capacity Credits. These allow a set number of requests over a period (default 2 days). | | WAIT_FOR_KEY_INTERVAL | Wait time in milliseconds if no private keys are available. | | TIME_TO_RELEASE_KEY | Time to wait before releasing the key after requesting it. | | RUN_IN_BAND | Run all tests in a single thread. | | RUN_IN_BAND_INTERVAL | The interval in milliseconds to run the tests in a single thread. | | LIT_RPC_URL | The URL of the Lit RPC server: - For local Anvil: http://127.0.0.1:8545 - For Chronicle: https://chain-rpc.litprotocol.com/http - For Yellowstone: https://yellowstone-rpc.litprotocol.com | | STOP_TESTNET | Flag to stop a single running testnet after the test run concludes. | | USE_SHIVA | A flag to determine if Shiva should be used for the local custom network. | | PRIVATE_KEYS | A set of private keys to use which will be used to perform chain operations. | | CHUNK_SIZE | Determines the number of tests run concurrently during parallel execution |

Below is the API Documentation for the ProccessEnvs interface for the shiva-client detailing the configurable environment variables and their purposes:

| Variable | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------- | | TESTNET_MANANGER_URL | URl to connect to Shiva (our testing tool for network management). | | LIT_NODE_BINARY_PATH | Binary path for the lit node version you wish to run. | | LIT_Action_BINARY_PATH | Binary path for the lit node version you wish to run. | | USE_LIT_BINARIES | Flag to indicate if a binary path should be used for testnet spawning or if it should be built from source. | | STOP_TESTNET | Flag to stop a single running testnet after the test run concludes. |

Writing a test

Writing a test is the same as writing any other code, except that you must throw an error if any occur. There are no assertion libraries, so all tests are written using basic if-else statements.

In the test function, a devEnv variable will automatically be added as the first parameter to your function.

Using the devEnv API in the test

export const testExample = async (devEnv: TinnyEnvironment) => {

  // ========== Enviorment ==========
  // This test will be skipped if we are testing on the DatilDev network
  devEnv.setUnavailable(LIT_NETWORK.DatilDev);

  // Using litNodeClient
  const res = await devEnv.litNodeClient.executeJs({...});

  // ========== Creating a new identify/user profile ==========
  const alice = await devEnv.createRandomPerson();

  // Alice minting a capacity creditrs NFT
  const aliceCcNft = await alice.mintCapacityCreditsNFT();

  // Alice creating a capacity delegation authSig
  const aliceCcAuthSig = await alice.createCapacityDelegationAuthSig();
};

TinnyPerson Class API

The TinnyPerson class encapsulates various functionalities to manage wallet operations, authentication, and contract interactions for testing purposes. Below is a detailed API documentation:

Alice's Properties

| Property | Description | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | privateKey | The private key used to instantiate the wallet associated with the TinnyPerson instance. | | wallet | An ethers.Wallet instance created using the provided privateKey and connected to the specified provider. | | siweMessage | A string that holds the Sign-In with Ethereum (SIWE) message used for authentication. | | pkp | EOA/Hot wallet owned PKP NFT | | authSig | An AuthSig object that stores the authentication signature derived from the SIWE message. | | authMethod | An AuthMethod object representing the authentication method used, typically related to blockchain wallet authentication. | | authMethodOwnedPkp | PKP information specifically tied to the authentication method of the wallet. | | contractsClient | An instance of LitContracts, used to interact with Lit Protocol smart contracts for operations such as minting tokens or PKP NFTs. | | provider | An ethers.providers.JsonRpcProvider instance connected to the blockchain network specified in envConfig. | | loveLetter | A Uint8Array containing a keccak256 hashed value, typically used as unsigned data to be passed to the executeJs and pkpSign functions |

Methods

| Method | Description | | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | constructor({privateKey, envConfig}) | Initializes a new instance of TinnyPerson with the specified private key and environment configuration. Sets up the wallet and provider based on these settings. | | spawn() | Performs several operations to set up the TinnyPerson instance fully, including authentication and contract client setup. It also mints a PKP using the specified authentication method. | | mintCapacityCreditsNFT() | Mints a Capacity Credits NFT based on the REQUEST_PER_KILOSECOND setting in envConfig. Returns the token ID of the minted NFT. | | createCapacityDelegationAuthSig(addresses) | Mints a Capacity Credits NFT and creates an authentication signature for delegating capacity, which can be used to authorize other addresses to use the minted credits. |

esbuild benchmark

// test-bundle-speed.ts
export const testBundleSpeed = async (devEnv: TinnyEnvironment) => {
  const a = await import('@lit-protocol/lit-node-client');
  const b = await import('@lit-protocol/contracts-sdk');
  const c = await import('@lit-protocol/auth-helpers');
  const d = await import('@lit-protocol/constants');
  const e = await import('@lit-protocol/lit-auth-client');

  console.log(a, b, c, d, e);
};
// ----------------
// Build time: 77ms
// ----------------