ck-dev@lists.openstack.org>>
Date: Wednesday, June 25, 2014 at 5:06 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [QA] Questions about test policy for scenario test
Good to know
;>
Subject: Re: [openstack-dev] [QA] Questions about test policy for scenario test
Good to know. I think it's a good idea to implement a common compute verifier
after instances booted. Maybe we can define different checking levels so that
it can be leveraged by different test cases. I will see wh
Good to know. I think it's a good idea to implement a common compute
verifier after instances booted. Maybe we can define different checking
levels so that it can be leveraged by different test cases. I will see
what I can do.
On 24/06/14 22:27, Sean Dague wrote:
> On 06/24/2014 01:29 AM, Fei Long
- Original Message -
> From: "Fei Long Wang"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: br...@catalyst.net.nz
> Sent: Tuesday, June 24, 2014 8:29:03 AM
> Subject: [openstack-dev] [QA] Questions about test policy fo
On 06/24/2014 01:29 AM, Fei Long Wang wrote:
> Greetings,
>
> We're leveraging the scenario test of Tempest to do the end-to-end
> functional test to make sure everything work great after upgrade,
> patching, etc. And We're happy to fill the gaps we found. However, I'm a
> little bit confused abou
Greetings,
We're leveraging the scenario test of Tempest to do the end-to-end
functional test to make sure everything work great after upgrade,
patching, etc. And We're happy to fill the gaps we found. However, I'm a
little bit confused about the test policy from the scenario test
perspective, esp
