[openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

Jordan Pittier jordan.pittier at scality.com
Tue Sep 27 10:06:58 UTC 2016


Hi,

On Tue, Sep 27, 2016 at 11:43 AM, milanisko k <vetrisko at gmail.com> wrote:

> Dear Stackers,
> I'd like to gather some overview on the $Sub: is there some infrastructure
> in place to gather such stats? Are there any groups interested in it? Any
> plans to establish such infrastructure?
>
I am working on such a tool with mixed results so far. Here's my approach
taking let's say Nova as an example:

1) Print all the routes known to nova (available as a python-routes object:
 nova.api.openstack.compute.APIRouterV21())
2) "Normalize" the Nova routes
3) Take the logs produced by Tempest during a tempest run (in
logs/tempest.txt.gz). Grep for what looks like a Nova URL (based on port
8774)
4) "Normalize" the tested-by-tempest Nova routes.
5) Compare the two sets of routes
6) ????
7) Profit !!

So the hard part is obviously the normalizing of the URLs. I am currently
using a tons of regex.... :) That's not fun.

I'll let you guys know if I have something to show.

I think there's real interest on the topic (it comes up every year or so),
but no definitive answer/tool.

Cheers,
Jordan

-- 
 
<https://www.scality.com/backup/?utm_source=signatures&utm_medium=email&utm_campaign=backup2016>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160927/bb14336c/attachment.html>


More information about the OpenStack-dev mailing list