Hi Eugene,
as you have already noticed there's already some overlap with your work
and the current tests development.
We should find a productive way to coordinate the efforts.
Thanks for starting the refactoring, in my opinion it's needed.
cheers,
Rossella
On Sat, Dec 14, 2013 at 4:53 PM, Jay
On Sat, 2013-12-14 at 19:09 +0400, Eugene Nikanorov wrote:
> Hi Jay,
>
> Sure, that is understood. In fact such refactoring could be a big
> change so I'd split it to two or more patches.
> Hope this will not overlap with ongoing neutron API tests development.
Hehe, given the sheer number of new
Hi Jay,
Sure, that is understood. In fact such refactoring could be a big change so
I'd split it to two or more patches.
Hope this will not overlap with ongoing neutron API tests development.
Thanks,
Eugene.
On Sat, Dec 14, 2013 at 7:01 PM, Jay Pipes wrote:
> On Sat, 2013-12-14 at 15:26 +040
On Sat, 2013-12-14 at 15:26 +0400, Eugene Nikanorov wrote:
> Hi tempest folks,
>
> While adding new API tests for Neutron I found out that network client
> used in tempest could be improved in at least two ways:
> 1) code duplication between xml and json versions could be removed
> 2) client API c
Hi tempest folks,
While adding new API tests for Neutron I found out that network client used
in tempest could be improved in at least two ways:
1) code duplication between xml and json versions could be removed
2) client API could be made more flexible and similar to real neutron
client API.
E.g.
