| commit | 2e24c3e1baa657bab7cb059ef5b66df4f4103a4d | [log] [tgz] |
|---|---|---|
| author | zhufl <zhu.fanglei@zte.com.cn> | Thu Nov 24 14:46:42 2016 +0800 |
| committer | zhufl <zhu.fanglei@zte.com.cn> | Thu Nov 24 17:38:07 2016 +0800 |
| tree | 557882f0ee99507b168bb6f1b02e515dac6ed7fc | |
| parent | 86cfa35b84be972802170aa78b8f0f1adadf21df [diff] |
Use names containing "non-existing" as non-existing resource names In test_list_servers_by_non_existing_flavor, 1234 is used as non_existing_flavor, but it is not strange if someone happens to use 1234 as flavor id in his environment. Besides, we can use names containing 'non-existing' instead of a hard-coded strange name for non-existing image/server/flavor names, which will make code looks more clear. Change-Id: I97e5a8723a77b5e5626ec20b439a5e6ce729d511