@loadsy/cli

 

Loadsy

About   |   Requirements   |   Starting   |   Commands   |   Author

🎯 About

Loadsy CLI tool to send tests to worker

✅ Requirements

Before starting 🏁, 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.

🏁 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

💻 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 ❤️ by Paxico Team

 

Back to top