2:39 p.m.
I'd say Golang client is the most mature as it's the only one in production use ;)
(and those production use-cases are included in its tests). But of course it's metrics
only.
Metrics itself has large amount of rest-tests, so repeating all of those makes no sense.
They could be run against a live Hawkular Services instance though.
- Micke
----- Original Message -----
From: "Lucas Ponce" <lponce(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, May 24, 2016 3:27:52 PM
Subject: Re: [Hawkular-dev] the new hawkular services distro
----- Mensaje original -----
De: "Heiko W.Rupp" <hrupp(a)redhat.com>
Para: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Enviados: Martes, 24 de Mayo 2016 14:24:51
Asunto: Re: [Hawkular-dev] the new hawkular services distro
On 24 May 2016, at 10:48, Juraci Paixão Kröhling wrote:
> Let me put my QE hat and share my thoughts: Hawkular Services REST
> endpoints is what we expose as API to other clients, like agents, the
> Go
> client, the Ruby client and so on. What is done "inside" doesn't
> matter
> much, as long as this API is stable. So, I'd build a set of use cases
> and do a set of independent test cases, which could in turn be run by
> CI/CD platform.
+1
In fact the ruby-client's test suite already tests a lot of this (*) and
could be used for this purpose
*) Standard operation mode is though to run against recorded cassettes,
so we would need to invest a bit more to reliably run with live-requests
against hawkular-services
+1
I like the idea to maintain the itest on the component to focus on pure REST API specifics
and use the client(s) (ruby here as it is most mature, but this can change on the future)
to test a wider integration test usecases.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev