Summary:
* Jay could not attend so there was no discussion of tempest gating or
Skip Captain or working with developers on functional test plans
* Jose will submit a hopefully final patch for the swift tests very soon
* We will standardize expected exception behavior to use assertRaises
rather than explicit try/catch. Unlike other assert unittest functions, this
one does not take an optional message so we will create a helper
method on a new TempsetTestCase that BaseComputeTest and friends
will inherit. This class will probably be used for other things as well.
* We will provide a mechanism on the clients to track resources and
"garbage collect" them when a test finishes running. It will still be
possible to
manage the resources manually if desired.
* Daryl is working on making parallel tempest execution work and will be
submitting changes in batches. The first one is:
https://review.openstack.org/#/c/7984/
* We did not have time to discuss the progress of a good example
blueprint for QA functional test plan
* The jenkins tempest job is failing on test_networks as reported in
https://bugs.launchpad.net/tempest/+bug/1007076. This should be fixed ASAP.
On 6/1/2012 12:37 AM, Karajgi, Rohit wrote:
Hi David,
Could you please give a summary of yesterday's meeting? There were
some key points discussed as per Daryl's email below.
Thanks!
Rohit
*From:*openstack-qa-team-bounces+rohit.karajgi=nttdata....@lists.launchpad.net
[mailto:openstack-qa-team-bounces+rohit.karajgi=nttdata....@lists.launchpad.net]
*On Behalf Of *Daryl Walleck
*Sent:* Thursday, May 31, 2012 9:52 PM
*To:* David Kranz
*Cc:* openstack-qa-team@lists.launchpad.net
*Subject:* Re: [Openstack-qa-team] Weekly Meeting tomorrow, Thursday,
May 31 @ 17:00 UTC
I'd like to add two agenda items/thoughts:
* Standardization of how we check for exceptions. Right now
try/except/pass, assertRaises, and decorators for expected
exceptions. It would be more understandable if we had one agreed
methodology to make our code more consistent
* Standardization of resource cleanup. Right now we have try/except
blocks around many tests and others creating lists of resources to
be disposed of during teardown. While I much prefer the latter
approach, we should standardize on a methodology again for
consistency.
Daryl
On May 30, 2012, at 4:07 PM, David Kranz wrote:
The weekly QA Team meeting takes place at 17:00 UTC on IRC
(#openstack-meeting on Freenode). We invite anyone interested in
testing, quality assurance and performance engineering to attend the
weekly meeting.
The agenda for this week is as follows:
* Review of last week's action items
- Ravikumar_hp to find good example blueprint for QA functional test
plan
- jaypipes to write draft email to ML about QA team working with
developers on functional test plans for all new feature blueprints.
- jaypipes to create Skip Captain duties wiki page and rotation
* Blockers preventing work from moving forward
- When can the Tempest gate job be turned on?
* Outstanding code reviews
Review all outstanding code reviews in the queue:
https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z
* New items for discussion
- Status of Swift tests
- Making parallel tempest runs really work
* Work in progress that will be landing soon
- Smoke testing base classes
- Swift tests
* Open discussion
Thanks,
-David
_______________________________________________
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openst...@lists.launchpad.net
<mailto:openst...@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~openstack-qa-team
<https://launchpad.net/%7Eopenstack-qa-team>
Post to : openstack-qa-team@lists.launchpad.net
<mailto:openstack-qa-team@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack-qa-team
<https://launchpad.net/%7Eopenstack-qa-team>
More help : https://help.launchpad.net/ListHelp
______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest
confidence for the sole use of the addressee and may contain legally
privileged, confidential, and proprietary data. If you are not the
intended recipient, please advise the sender by replying promptly to
this email and then delete and destroy this email and any attachments
without any further use, copying or forwarding
--
Mailing list: https://launchpad.net/~openstack-qa-team
Post to : openstack-qa-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help : https://help.launchpad.net/ListHelp
