Bucky Command

Bucky Command

Command List

• new
• make service
• make page
• lint
• run
• rerun

new

Create a working directory for Bucky's test code, includes the config files that Bucky needs.

Usage: new PROJECT_NAME

Directory structure under PROJECT_NAME will be like below:

PROJECT_NAME
├── config
│   ├── bucky_config.yml
│   ├── e2e_config.yml
│   ├── linkstatus_config.yml
│   └── test_db_config.yml
├── services
│   └── README.md
└── system
    ├── evidences
    │   ├── README.md
    │   └── screen_shots
    │       └── README.md
    └── logs
        └── README.md

make service

Notice: This command works only in working directory.

Create a new directory under services directory.

Usage: make service SERVICE_NAME

Directory structure will be like below:

PROJECT_NAME
└──services
    └── SERVICE_NAME

make page

Notice: This command works only in working directory.

Create pageobject file and part file. Also create directory for each kind of file if there doesn't exist.

Usage: make page [options] PAGE_NAME

Options:
    --service, SERVICE_NAME    (Required) Target service directory.
    --device, DEVICE           (Optional) Target device directory. DEVICE should be pc, sp or tablet.
                               (default: pc)

Directory structure will be like below:

PROJECT_NAME
└──services
    └── SERVICE_NAME
        └── pc
            ├── pageobject
            │   └── PAGE_NAME.rb
            └── parts
                └── PAGE_NAME.yml

lint

Notice: This command works only in working directory.

Check syntax for Bucky.

Usage: lint [options]

Options:
    -C, --category CATEGORY_NAME    (Optional) Target file type.
                                    Type must be one of:
                                      config: config file under config directory.
                                    (default: config)

run

Notice: This command works only in working directory.

Run a job that execute test code under scenario directory.

Usage: run [options]

Options:
    -d, --debug    (Optional) It won't insert test result into DB.
                    Without this option, you should have been set up Bucky-management for DB.
    -t, --test_category TEST_CATEGORY    (Optional) Filter for the test code to run.
    -s, --suite_name SUITE_NAME    (Optional) Filter for the test code to run.
    -S, --service SERVICE    (Optional) Filter for the test code to run.
    -c, --case CASE_NAME    (Optional) Filter for the test code to run.
    -D, --device DEVICE    (Optional) Filter for the test code to run.
    -p, --priority PRIORITY    (Optional) Filter for the test code to run.
    -l, --label LABEL_NAME    (Optional) Filter for the test code to run.
    -r, --re_test_count RE_TEST_COUNT    (Optional) How many rounds you run tests.
                                          Only the failure test will be executed in next round.
                                          Notice: It use default value when option --debug had set.
                                          (default: 1)
    -m, --link_check_max_times MAX_TIMES    (Optional) Max check times for same URL in Linkstatus. Works only with which test_category is Linkstatus.
                                            (default: 3)

rerun

Notice:

• This command works only in working directory.
• You should have been set up Bucky-management for DB.

Rerun the failure test code in a job according to the record in DB.

Usage: rerun [options]

Options:
    -j, --job_id JOB_ID    (Required) The ID of job which is recorded in DB.
    -d, --debug    (Optional) It won't insert test result into DB.
                    Without this option, you should have been set up Bucky-management for DB.
    -r, --re_test_count RE_TEST_COUNT    (Optional) How many rounds you run tests.
                                          Only the failure test will be executed in next round.
                                          Notice: It use default value when option --debug had set.
                                          (default: 1)