Hi,
In the last design summit, I had introduced some of our efforts for Performance
Testing of OpenStack using Jmeter.
I was interested to how know if this can be made a part of Tempest. There is a
stress test framework that already is
present in Tempest, and it can be run with some nose attrib
Wow, that answers everything.
Thanks Jim!
-Rohit
-Original Message-
From: James E. Blair [mailto:cor...@inaugust.com]
Sent: Thursday, August 02, 2012 9:03 PM
To: Karajgi, Rohit
Cc: openstack-qa-team@lists.launchpad.net; Patil, Tushar
Subject: Re: [Openstack-qa-team] Viewing Devstack
Hi,
I was interested to know if there is any way to see the OpenStack service logs
(not the Build console logs) that the Tempest gate jobs run against?
I have faced a couple of situations in which the gate-tempest-devstack-vm job
fails but I was unable to reproduce the exact error on my local se
Hi David,
Could you please give a summary of yesterday's meeting? There were some key
points discussed as per Daryl's email below.
Thanks!
Rohit
From: openstack-qa-team-bounces+rohit.karajgi=nttdata@lists.launchpad.net
[mailto:openstack-qa-team-bounces+rohit.karajgi=nttdata@lists.launc
Great news indeed :)
Cheers,
Rohit
-Original Message-
From: openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net
[mailto:openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net] On
Behalf Of Daryl Walleck
Sent: Friday, May 04, 2012 9:01 PM
To: Jay Pipes
Cc: ; openst..
If the approach would be to use the client tools to "only smoke test" the
Openstack API, I would somewhat
agree. I think the smoke tests should be shallow but wide, covering every API
in OpenStack but not ever 'scenario'.
So to me a "subset of test cases" would be a subset of "test cases from eve
Hi,
What is the policy that we should or are following for test cases that fail due
to an existing Open Bug in Launchpad?
For eg:
https://github.com/openstack/tempest/blob/master/tempest/tests/test_list_floating_ips.py#L64
skips the test and posts the Bug ID in the message.
Do we submit the te
PM
To: openstack-qa-team@lists.launchpad.net
Subject: Re: [Openstack-qa-team] Devstack dependent tests
On 04/30/2012 09:24 AM, Karajgi, Rohit wrote:
> The coverage can be expanded quite a bit by having tests that perform certain
> 'white-box' actions such as updating DB entries, an
h as resize_available) it would be better to introduce a new config
variable rather than making people tweak the arguments to nose. I also think
the default for tempest should be that it is not using devstack.
-David
On 4/30/2012 12:25 AM, Karajgi, Rohit wrote:
> Hi,
>
> We are writing
Hi,
We are writing new tests for keystone and some of these tests need to touch
keystone database.
I really want to avoid this, but unfortunately there are no RESTful APIs
supported in stable/essex to do the job.
One of the example is
1. Check if get_tenants api fails for expired token. T
10 matches
Mail list logo
