Open Stack

Good point.

A change in the configuration will be gated by a Jenkins run like any other
change, so it should not be merged if it breaks.
However it will indeed postpone the verification of the tests to the time
where the configuration change is done.

andrea

-----Original Message-----
From: David Kranz [mailto:david.kranz at qrclab.com] 
Sent: 20 February 2013 15:29
To: openstack-qa at lists.openstack.org
Subject: [openstack-qa] Adding new tests to the gate

Now that every test added to Tempest is gating all projects, we have to be
even more careful. There have been some submissions of new tests to Tempest
in  a state where they are skipped due to some configuration that is not
(yet) set in the devstack gate configuration. This introduces the risk that
when some one tries to change the configuration to support the new tests,
there will be failures. It would be better to turn on the configuration in
the devstack gate first, and then submit tests.

The most recent example I saw was for the v3 keystone tests. What is needed
to enable these tests in the gate?

  -David

_______________________________________________
openstack-qa mailing list
openstack-qa at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6202 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-qa/attachments/20130220/c2e8fcd0/attachment.bin>