From b2423a024bd3ae8c968869aeca651f0b5a7ba749 Mon Sep 17 00:00:00 2001 From: debugtalk Date: Sat, 26 Aug 2017 23:07:35 +0800 Subject: [PATCH] rename CLI name: ate-locust => locusts --- README.md | 6 +++--- setup.py | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index ee8543b8..fb3dec55 100644 --- a/README.md +++ b/README.md @@ -220,16 +220,16 @@ $ ate filepath/testcase.yml --report-name ${BUILD_NUMBER} \ With reuse of [`Locust`][Locust], you can run performance test without extra work. ```bash -$ ate-locust -V +$ locusts -V Locust 0.8a2 ``` -For full usage, you can run `ate-locust -h` to see help, and you will find that it is the same with `locust -h`. +For full usage, you can run `locusts -h` to see help, and you will find that it is the same with `locust -h`. The only difference is the `-f` argument. If you specify `-f` with a Python locustfile, it will be the same as `locust`, while if you specify `-f` with a `YAML/JSON` testcase file, it will convert to Python locustfile first and then pass to `locust`. ```bash -$ ate-locust -f examples/first-testcase.yml +$ locusts -f examples/first-testcase.yml [2017-08-18 17:20:43,915] Leos-MacBook-Air.local/INFO/locust.main: Starting web monitor at *:8089 [2017-08-18 17:20:43,918] Leos-MacBook-Air.local/INFO/locust.main: Starting Locust 0.8a2 ``` diff --git a/setup.py b/setup.py index b8b144c7..4b502e24 100644 --- a/setup.py +++ b/setup.py @@ -54,7 +54,7 @@ setup( entry_points={ 'console_scripts': [ 'ate=ate.cli:main_ate', - 'ate-locust=ate.cli:main_locust' + 'locusts=ate.cli:main_locust' ] } )