Run tests in CLI using Akto
You can also run Akto testing module on your CLI.
When to use
You can use the CLI if you want to run Akto tests locally on any API Collection.
The results from the CLI are NOT saved in Akto dashboard.
It is best used when developers want to run tests locally before committing to their branch. Note that the application host is chosen as in the API Collection by default.
You choose to override the application host url to localhost or a different staging URL.
How to use
Prepare the following environment vars -
AKTO_API_KEY
- Go to My accounts > Settings > Integrations > Akto API > Generate token. Copy the token generated.AKTO_DASHBOARD_URL
- URL of your dashboard. Please ensure you can access dashboardTEST_IDS
- Space-separated list of test IDs which you want to run eg.JWT_NONE_ALGO REMOVE_TOKENS
. You can also set it asALL
to run all tests.API_COLLECTION_NAME
- API collection name on which you want to run tests eg. juice_shop_demo.API_COLLECTION_ID
- API collection id (integer) you want to run tests eg. 29623412. Only one ofAPI_COLLECTION_NAME
andAPI_COLLECTION_ID
is required.TEST_APIS
- Space-separated list of APIs you want to test. If absent, all APIs are selectedOVERRIDE_APP_URL
- change the staging application host. Akto will test APIs on this hostOUTPUT_LEVEL
- Output level of the result file. We have 4 output levels:NONE
- No output file is generated.SUMMARY
- [Default] The output file contains the tests executed and a list of all vulnerable APIs.DETAILED
- The output file contains theSUMMARY
as well as description and impact of the executed tests.DEBUG
- The output file containsDETAILED
output along with the original and attempt request and response for all the API tests.
Example CLI - (If you are not on Linux, please provide absolute path to your current directory instead of ${PWD})
Results
A short summary (API, Vulnerability, Severity) is printed on command line itself
A file
output.txt
contains details of the test, based on the output level given.If you see version mismatch error, consider matching release version of your dashboard vs testing-cli
Sample results -
Limitations
Results are not saved in Akto dashboard.
Tests which use context will be skipped eg.
AddUserId.yml
,OldApiVersion.yml
etc.
Last updated