I think we should remove these tests, even though tempest run in serial.
Because we can't assume the enable service action will be successful.
(But on the other hand, one test is failed, the tempest gate will be
failed. We need find it out and fix it. :-) )
On 2013?11?13? 10:23, Zhi Kun
hi, Chris thanks for your work.
It's a good way. And how about creating a blue-print and putting these
link on it? Some guys have been familiar with looking for work items
from blue-print, and writing something in hacking guide may be better.
On 2013?10?30? 21:10, Christopher Yeoh wrote:
Hi,
I also collect the tests status for nova v3 api manually. You can find
the status of v3 tests in this link:
https://etherpad.openstack.org/p/nova-v3-tests
Because there are some extensions that just extend the attribute of
specific api reponse, or convert some input before specific api
hi,
I'm working on bp:nova-v3-tests in tempest. The nova tests in
tempest mostly have been ported into v3 and sent off.
but we got some feedbacks that there was mass code duplication and
suggested to do this by inheritance.
So I have sent another patch to do this by inheritance. But in
