Tempest test scenarios are insufficient

Bug #1694181 reported by Hiroaki Kobayashi on 2017-05-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Medium
Pierre Riteau

Bug 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 (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.

Masahito Muroi (muroi-masahito) wrote :

Could you describe or list what scenarios are missing? I want to add this the milestone for 0.3.0 when the scenarios are clear. It's better for this kind of bug reports to be actionable.

I've added test scenarios. Please check if they are sufficient.

description: updated
Changed in blazar:
milestone: none → 0.3.0
description: updated
Pierre Riteau (priteau) on 2017-05-30
summary: - Tempest test scenarios are insafficient
+ Tempest test scenarios are insufficient
Changed in blazar:
importance: Undecided → Medium
Pierre Riteau (priteau) on 2017-05-30
Changed in blazar:
status: New → Confirmed
Masahito Muroi (muroi-masahito) wrote :

All the scenarios are targeted to Queens release.

Changed in blazar:
milestone: 0.3.0 → 0.4.0

Reviewed: https://review.openstack.org/482532
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=adeb401abcd967bd8a1d602c1b74067a15d9d901
Submitter: Zuul
Branch: master

commit adeb401abcd967bd8a1d602c1b74067a15d9d901
Author: Maho Koshiya <email address hidden>
Date: Sat Jul 1 08:11:28 2017 +0900

    Add scenario test of lease expiration

    The reserved host for blazar users are released when the lease expires,
    and host aggregate that created for Blazar is deleted.
    Check the instance created during the expiration has been removed
    by release of host.

    Change-Id: Ied3c766a1d7d839eb4301b494e4b35c75151f242
    Partial-bug: #1694181

Reviewed: https://review.openstack.org/490351
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=5cd53f330879187fc43899db406bf30c65d95915
Submitter: Zuul
Branch: master

commit 5cd53f330879187fc43899db406bf30c65d95915
Author: Maho Koshiya <email address hidden>
Date: Wed Jul 5 07:41:29 2017 +0900

    Add a termination scenario test

    When the user specifies end_time and executes update API,
    check that resources are correctly released at lease end time.
    It confirm that the instance created during the lease period
    have been removed by lease end.

    Change-Id: Ic1076905ad5f2fc894036b045743eacb5c2db9bd
    Partial-bug: #1694181

Changed in blazar:
milestone: 0.4.0 → queens-3
Changed in blazar:
milestone: queens-3 → rocky-1
Pierre Riteau (priteau) on 2018-09-10
Changed in blazar:
assignee: nobody → Pierre Riteau (priteau)
milestone: rocky-1 → stein-1
Pierre Riteau (priteau) on 2018-10-23
Changed in blazar:
milestone: stein-1 → stein-2
Pierre Riteau (priteau) on 2019-01-10
Changed in blazar:
milestone: stein-2 → stein-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers