Sorry for late reply... in Bulgaria on vacation until 29th... Comments
inline.
On 08/16/2012 08:13 PM, David Kranz wrote:
> I think this clearly illustrates why it is so important for QA to be
> done more in the open, and to post tempest blueprints for largish
> projects like this. I have a theo
I think this clearly illustrates why it is so important for QA to be
done more in the open, and to post tempest blueprints for largish
projects like this. I have a theory that one important reason so many
organizations choose not to do this is that once they submit their tests
to the public rep
Hi Daryl,
DW> Sorry for any confusion.
I share at least half the blame here :/
DW> I've had an implementation for this working for awhile, but failed
DW> to port it in as I was working on getting other features
DW> out. Regardless of the implementation, I'm really happy to see this
DW> flexibili
Hi Dan,
Sorry for any confusion. I've had an implementation for this working for
awhile, but failed to port it in as I was working on getting other features
out. Regardless of the implementation, I'm really happy to see this flexibility
get intoTempest trunk. Since it seems you and your team ha
Hi all,
I've been working on XML API tests for tempest all week, after the
decision in the Nova meeting last week that XML needs to be supported
and tested. When I happened through #openstack-meeting today, I realized
I had missed a QA meeting where it was discussed that Daryl Walleck had
a bunch
5 matches
Mail list logo
