| 2017-05-29 02:37:42 |
Hiroaki Kobayashi |
bug |
|
|
added bug |
| 2017-05-30 02:16:44 |
Hiroaki Kobayashi |
description |
There is only one scenario for the tempest test. More scenarios should be added. |
There is only one scenario for the tempest test. Following scenarios are needed for the host reservation:
* Lease expiration test: Check if all resources related to the lease are correctly released with the expiration of the lease.
* Lease termination test: Check if all resources related to the lease are correctly released at the time a user terminates the lease by delete_lease or update_lease request.
* Lease update test (time): Check if an update lease request is correctly processed.
* Lease update test (capacity): Check if an update lease request is correctly processed.
* before_end actions test: Check if before_end actions are successfully executed at the before_end_date.
* Request failure test: Check if the Blazar returns errors where a request is invalid. |
|
| 2017-05-30 02:20:20 |
Hiroaki Kobayashi |
blazar: milestone |
|
0.3.0 |
|
| 2017-05-30 02:22:46 |
Hiroaki Kobayashi |
description |
There is only one scenario for the tempest test. Following scenarios are needed for the host reservation:
* Lease expiration test: Check if all resources related to the lease are correctly released with the expiration of the lease.
* Lease termination test: Check if all resources related to the lease are correctly released at the time a user terminates the lease by delete_lease or update_lease request.
* Lease update test (time): Check if an update lease request is correctly processed.
* Lease update test (capacity): Check if an update lease request is correctly processed.
* before_end actions test: Check if before_end actions are successfully executed at the before_end_date.
* Request failure test: Check if the Blazar returns errors where a request is invalid. |
There is only one scenario for the tempest test. Following scenarios are needed for the host reservation:
* Lease expiration test: Check if all resources related to the lease are correctly released with the expiration of the lease.
* Lease termination test: Check if all resources related to the lease are correctly released at the time a user terminates the lease by delete_lease or update_lease request.
* Lease update test (time): Check if an update lease request is correctly processed.
* Lease update test (capacity (this feature is addressed by https://blueprints.launchpad.net/blazar/+spec/update-reserved-capacity)): Check if an update lease request is correctly processed.
* before_end actions test: Check if before_end actions are successfully executed at the before_end_date.
* Request failure test: Check if the Blazar returns errors where a request is invalid. |
|
| 2017-05-30 08:03:05 |
Pierre Riteau |
summary |
Tempest test scenarios are insafficient |
Tempest test scenarios are insufficient |
|
| 2017-05-30 09:23:11 |
Masahito Muroi |
blazar: importance |
Undecided |
Medium |
|
| 2017-05-30 09:24:42 |
Pierre Riteau |
blazar: status |
New |
Confirmed |
|
| 2017-09-01 08:12:07 |
Masahito Muroi |
blazar: milestone |
0.3.0 |
0.4.0 |
|
| 2018-02-09 06:52:38 |
Masahito Muroi |
blazar: milestone |
0.4.0 |
queens-3 |
|
| 2018-03-02 16:23:17 |
Masahito Muroi |
blazar: milestone |
queens-3 |
rocky-1 |
|
| 2018-09-10 21:12:07 |
Pierre Riteau |
blazar: assignee |
|
Pierre Riteau (priteau) |
|
| 2018-09-10 21:12:17 |
Pierre Riteau |
blazar: milestone |
rocky-1 |
stein-1 |
|
| 2018-10-23 10:18:02 |
Pierre Riteau |
blazar: milestone |
stein-1 |
stein-2 |
|
| 2019-01-10 14:50:06 |
Pierre Riteau |
blazar: milestone |
stein-2 |
stein-3 |
|
| 2019-04-15 17:58:28 |
Pierre Riteau |
blazar: milestone |
stein-3 |
train-1 |
|
