Hi,
We have come up with a mechanism to include automated tests for the REST
API which is going to be shipped with APIM 1.10.0. This is a data driven
test mechanism. The purpose of this E-Mail is to communicate the method
that we used to do the required task.
The test automation process has
Excellent job Chamin.
This will be really cool module and we can use it for all REST API test
scenarios across platform.
Thanks,
sanjeewa.
On Mon, Dec 14, 2015 at 11:00 AM, Chamin Dias wrote:
> Hi,
>
> We have come up with a mechanism to include automated tests for the REST
Hi Sanjeewa,
Sorry for late reply , some how i missed this.
Please use following versions on dependencies
2.0.0.wso2v1
3.0.2.Final
2.0.1
And place the dependency with scope of compile so that won't conflict with
other dependencies.
org.jboss.resteasy
resteasy-client
compile
@dharshana can you confirm rest easy version we should use in Apim 1.10x.
It seems http client version conflict happen in automation tests due to
obove import.
Thanks
sanjeewa.
sent from my phone
On Nov 20, 2015 2:37 PM, "Dharshana Warusavitharana"
wrote:
> Hi Sanjeewa,
>
Hi Team,
While implementing test case as per sample provided by dharshanaW i wanted
add following dependencies to test back end pom.
javax.ws.rs
javax.ws.rs-api
2.0.1
org.jboss.resteasy
resteasy-client
Hi Sanjeewa,
This is ok to add these dependencies but for jax-rs please refer the jax-rs
wso2 version that used in the product. Else there will be confilcts.
Thank you,
Dharshana.
On Fri, Nov 20, 2015 at 2:29 PM, Sanjeewa Malalgoda
wrote:
> Hi Team,
> While implementing
As per discussion with automation test team our plan is to implement data
driven test cases for this.
With that we will be able to define request data and expected response
data.
The utility class we are going to implement will take request data and then
validate response with provided response.
Hi Sanjeewa
On Tue, Oct 20, 2015 at 2:47 PM, Sanjeewa Malalgoda
wrote:
> QAA team shall we have discussion on this and come to conclusion?
> Please let us know possible time slots.
>
+1 shall we meet this week.
Thanks,
Krishantha.
>
> Thanks,
> sanjeewa.
>
> On Mon, Oct
QAA team shall we have discussion on this and come to conclusion?
Please let us know possible time slots.
Thanks,
sanjeewa.
On Mon, Oct 19, 2015 at 12:44 PM, Sanjeewa Malalgoda
wrote:
> Here idea is easily manage the tests and web application.
> Since web application purely
Sorry mail got sent accidentally half written. will complete and send
shortly.
On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka wrote:
> Hi Sanjeewa
>
> Saneth & I had an offline chat regarding this last week there are few
> things we need to consider.
>
> 1. Generating
Is it right to auto-generate the test client code? IMO one objective of
this should be to make sure the REST APIs don't change across patch
releases, etc. If we auto-generate the test stubs we would loose that
advantage.
Thanks,
NuwanD.
On Mon, Oct 19, 2015 at 12:26 PM, Joseph Fonseka
Hi Team,
We are planning to implement complete REST API for all operations available
in API Manager.
This will be CXF based jax-rs application.
This application based on swagger template and service skeleton
automatically generate according to swagger to cxf implementation done by
Jo.
We would
On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda
wrote:
> Hi Team,
> We are planning to implement complete REST API for all operations
> available in API Manager.
> This will be CXF based jax-rs application.
> This application based on swagger template and service skeleton
Hi Sanjeewa
Saneth & I had an offline chat regarding this last week there are few
things we need to consider.
1. Generating integration test for the Jax-RS functionality ex . If crud
operations work, if it returns correct error messages.
- We can use swagger-codegen to do this.
API
Hi Sanjeewa,
Currently we are not using a mechanism to proceed testing with auto
generated clients. As I understand by the requirement this might subject to
change API definition posted by the application with changes in the product
level.
But as per the requirement I think it would be ideal if
Hi Sanjeewa
Saneth & I had an offline chat regarding this last week there are few
things we need to consider.
1. Generating integration test for the Jax-RS functionality ex . If crud
operations work, if it returns correct error messages.
- We can use swagger-codegen to do this.
Hi Nuwan
Thanks for pointing that out, in that case test can be version-ed so auto
generated tests for version 1.0.0 should work with API 1.0.1 ...
WDYT?
Regards
Jo
On Mon, Oct 19, 2015 at 12:29 PM, Nuwan Dias wrote:
> Is it right to auto-generate the test client code? IMO
Hi Jo,
If so the issue is how you eliminate the client generation on normal
product build. So if there is a requirement of maintaining API as it is it
is a bad idea it generate test client on demand.
So in bottom line you only expect API change for 1.0.0 in next main release
2.0.0. So this won't
Here idea is easily manage the tests and web application.
Since web application purely depend on swagger definition it will
automatically generate beans, service skeletons etc.
So in same way if we implement test cases we don't have to go and edit test
case code after we adding new parameters or
Hi Jo,
As per the practise we followed there won't be a big effort in migrating
these tests since we use base test methods to use these API calls. So we
can handle this without changing tests.
Thank you,
Dharshana.
On Mon, Oct 19, 2015 at 12:17 PM, Joseph Fonseka wrote:
>
20 matches
Mail list logo