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

@loadsy/cli

v2.0.9

Published

cli to run tests on loadsy api project

Downloads

29

Readme

 

:dart: About

Loadsy CLI tool to send tests to worker

:white_check_mark: Requirements

Before starting :checkered_flag:, you need to have Node installed and be version 12.18.4 ,to get the eslint working on tests files you need to install eslint globally or in the project folder.

:checkered_flag: Starting


# 1.Install Loadsy globally

$ npm install -g @loadsy/cli



# 2.Create a project folder

$ loadsy init my-first-test



# 3.Enter project folder

$ cd my-first-test



# 4.Create a js script on scripts folder

  var result = loadsy.get(
    'https://httpstat.us/201',
    { 'Content-Type': 'application/json' },
    'Get 201'
  );


# 4.1 to load a csv file add the file on resources directory and use loadsy.csv(<filename>.csv) to toad it on the test file as below

  var csvData = loadsy.csv("myTestsData.csv");


# 5.Create a new project

$ loadsy create project my-first-test



# 5.Upload the file to your project in our remote servers

$ loadsy test upload my-first-test



# 5.Run your test

$ loadsy test run my-first-test



:computer: Commands


# Login

$ loadsy login

# or


$ loadsy login -e <email> -p <password>


# Init a project folder (you can pass . to init in the current directory)

$ loadsy init <project-name>



# Create a new project

$ loadsy create project <project-name>



# Upload files to a project

$ loadsy test upload <project-name>



# 5.Run the project's default script

$ loadsy test run <project-name>



# or any other script in the scripts directory

$ loadsy test run -s <script-name> <project-name>


# Pass desired threads count or request per second flag

$ loadsy test run -tc <thread-count-number> <project-name>

# or

$ loadsy test run -rps <request-per-second-number> <project-name>


# Pass desired duration for the test in seconds

$ loadsy test run -d <duration> <project-name>


# Pass desired ramp up time for the test in seconds

$ loadsy test run -r <ramp-up-time> <project-name>

# Pass desired env file to load on test prod to load prod.env and stage to load stage.env if option is not passed no env file will be loaded

$ loadsy test run -e prod <project-name>

# or

$ loadsy test run -e stage <project-name>


# List all projects

$ loadsy list projects



# List all tests files from a project

$ loadsy list tests <project-name>



# Debug a test locally

$ loadsy debug <script-name>

# or you can pass the -e option to load a .env file

$ loadsy debug -e prod <script-name>

# or

$ loadsy debug -e stage <script-name>



Made with :heart: by Paxico Team

 

Back to top