A CLI to run Hoppscotch test scripts in CI environments.
npm install @hoppscotch/cliA CLI to run Hoppscotch Test Scripts in CI environments.
- hopp test [options] [file]: testing hoppscotch collection.json file
``bash`
hopp [options or commands] arguments
- -v, --ver: see the current version of the CLI-h
- , --help: display help for command
1. #### hopp -v / hopp --ver
- Prints out the current version of the Hoppscotch CLI
2. #### hopp -h / hopp --help
- Displays the help text
3. #### hopp test [options]
- Interactive CLI to accept Hoppscotch collection JSON path
- Parses the collection JSON and executes each requests
- Executes pre-request script.
- Outputs the response of each request.
- Executes and outputs test-script response.
#### Options:
##### -e, --env
- Accepts path to env.json with contents in below format:
`json`
{
"ENV1": "value1",
"ENV2": "value2"
}
- You can now access those variables using pw.env.get('
Taking the above example, pw.env.get("ENV1") will return "value1"
#### -d, --delay
- Used to defer the execution of requests in a collection.
#### --token
- Expects a personal access token to be passed for establishing connection with your Hoppscotch account.
#### --server
- URL of your self-hosted instance, if your collections are on a self-hosted instance.
#### --reporter-junit [path]
- Expects a file path to store the JUnit Report.
##### --iteration-count
- Accepts the number of iterations to run the collection
##### --iteration-data
- Accepts the path to a CSV file with contents in the below format:
`text`
key1,key2,key3
value1,value2,value3
value4,value5,value6
For every iteration the values will be replaced with the respective keys in the environment. For iteration 1 the value1,value2,value3 will be replaced and for iteration 2 value4,value5,value6 will be replaced and so on.
#### --legacy-sandbox
- Opt out from the experimental scripting sandbox.
The Hoppscotch CLI follows pre-1.0 semantic versioning conventions while in alpha (version < 1.0.0):
- Feature releases (e.g., 0.20.0 → 0.21.0): New features, enhancements, or improvements0.20.0
- Patch releases (e.g., → 0.20.1): Bug fixes, security patches, and minor improvements0.21.0
- Breaking changes (e.g., → 0.30.0): Major version-like bumps for backwards-incompatible changes
> Once the CLI reaches stability and a mature feature set, we will transition to standard semantic versioning starting with 1.0.0.
- Before you install Hoppscotch CLI you need to make sure you have the dependencies it requires to run.
- Windows & macOS: You will need node-gyp installed. Find instructions here: https://github.com/nodejs/node-gyp`
- Debian/Ubuntu derivatives:
sh`
sudo apt-get install python g++ build-essential
- Alpine Linux:
sh`
sudo apk add python3 make g++
- Amazon Linux (AMI)
sh`
sudo yum install gcc72 gcc72-c++
- Arch Linux
sh`
sudo pacman -S make gcc python
- RHEL/Fedora derivatives:
sh`
sudo dnf install python3 make gcc gcc-c++ zlib-devel brotli-devel openssl-devel libuv-devel
- Once the dependencies are installed, install @hoppscotch/cli from npm by running:
`
npm i -g @hoppscotch/cli
1. Clone the repository, make sure you've installed latest pnpm.
2. pnpm install
3. Build required workspace dependencies (if needed):
bash`
# These auto-build via postinstall hooks during 'pnpm install'
# Rebuild manually only when you make changes to these packages:
pnpm --filter @hoppscotch/data run build
pnpm --filter @hoppscotch/js-sandbox run build
4.
5.
6.
7. Test the installation by executing
When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
1. Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is SemVer.
4. You may merge the Pull Request once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer merge it for you.
1. After cloning the repository, execute the following commands:
`bash`
pnpm install
# Build required workspace dependencies (if needed)
# These auto-build via postinstall hooks during 'pnpm install'
# Rebuild manually only when you make changes to these packages:
pnpm --filter @hoppscotch/data run build
pnpm --filter @hoppscotch/js-sandbox run build
# Then build the CLI
cd packages/hoppscotch-cli && pnpm run build
2. In order to test locally, you can use two types of package linking:
1. The 'pnpm exec' way (preferred since it does not hamper your original installation of the CLI):
`bash
pnpm link @hoppscotch/cli
// Then to use or test the CLI:
pnpm exec hopp
// After testing, to remove the package linking:
pnpm rm @hoppscotch/cli
`
2. The 'global' way (warning: this might override the globally installed CLI, if exists):
`bash
sudo pnpm link --global
// Then to use or test the CLI:
hopp
// After testing, to remove the package linking:
sudo pnpm rm --global @hoppscotch/cli
`
3. To use the Typescript watch scripts:
`bash``
pnpm run dev