[Openstack-qa-team] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

2012-05-03 Thread Jay Pipes
Hi all, I'd like to get some alignment on the following: 1) The definition of what is a "smoke" test 2) How we envision the Tempest project's role in running such tests First, a discussion on #1. There seem to be very loose semantics used to describe what a "smoke test" is. Some groups use th

[Openstack-qa-team] Summary of QA Weekly Status meeting

2012-05-03 Thread David Kranz
The QA team had its weekly IRC meeting today. Here is a summary of the progress and decisions coming out of the meeting. * Progress There were a bunch of problems that were preventing the tempest gating job from running successfully. The last (:-) ) problem was identified. We hope to turn t

Re: [Openstack-qa-team] [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

2012-05-03 Thread Daryl Walleck
So my first question is around this. So is the claim is that the client tools are the default interface for the applications? While that works for coders in python, what about people using other languages? Even then, there's no guarantee that the clients in different languages are implemented in

Re: [Openstack-qa-team] [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

2012-05-03 Thread Daryl Walleck
Perhaps it's just me, but given if I was developing in a different language, I would not want to use a command line tool to interact with my application. What is the point then of developing RESTful APIs if the primary client is not it, but these command line tools instead? While it may appear