[Architecture] Notes: Architecture Review Test Automation Framework - 29th Sept, 2010

[Samisa Abeysinghe]

What is the latest on test automation framework? Any news? Have we completed
ESB? Have we started on G-Reg?

On Wed, Sep 29, 2010 at 8:24 PM, Srinath Perera <srinath at wso2.com> wrote:

> Main comment was to try to reduce the code and push more and more data
> for the test in to configs.
>
> For example, to test Proxies, we can write lot of test scenarios in
> java. Instead we can write a code that reads a folder, deploys a proxy
> inside the folder, and then send messages defined inside a sub folder
> to the deployed proxy service. The second implementation will use less
> code, and it is very easy to  new test scenarios by adding new
> folders/ xml files to define messages. Also some of the test
> scenarios, if they can be expressed as XML files, we can even
> generated randomly via a code.
>
> The same idea can be extended to other cases. Moto should be that
> "good programmers should be lazy, but in intelligent way (because they
> try to automate as much as possible)".
> --Srinath
>
> On Wed, Sep 29, 2010 at 5:05 PM, Thilini Ishaka <thilini at wso2.com> wrote:
> >
> > Hi All,
> >
> > Participants: Samisa, Srinath, Charitha, Chamara, Thilini
> >
> > We went through the ESB test automation framework architecture.
> > The mediator tests and esb-sample automation is in a satisfactory level
> and
> > is required improvements in following areas.
> >
> > Client side improvements
> > --------------------------------------
> > 1. Currently we are using the SimpleStockQuoteService which generates a
> SOAP
> > request. We need to improve the framework to accept different request
> types
> > like SOAP, REST, XML, JSON, etc.
> > 2. Need to have tests for different request sizes.(handle large requests)
> > 3. Need to have tests for different content types like application/xml,
> > text/xml, text/html, etc
> > 4. Need to have tests for different HTTP client methods. Currently we are
> > testing only for POST but need to test for GET as well.
> >
> > Server side improvements
> > --------------------------------------
> > 1. We need to focus on reasonable number of different negative test
> > scenarios as currently the negative test coverage is not in a
> satisfactory
> > level.
> > 2. We need to change following AdminService tests to accept xml as input
> and
> > derive the configuration based on that.
> >       EndpointAdmin, ProxyServiceAdmin, EventSourceAdmin,
> LocalentryAdmin,
> > SequenceAdmin
> > Also we need to improve other admin service tests.
> >
> > Thanks
> >
> >
> > Regards,
> >
> > Thilini Ishaka
> > Software Engineer
> > WSO2, Inc
> > email: thilini at wso2.com
> > mobile: 0718408171
> >
> >
> > _______________________________________________
> > Architecture mailing list
> > Architecture at wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >
> >
>
>
>
> --
> ============================
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Lecturer, University of Moratuwa
>   Member, Apache Software Foundation
>   Member, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20101101/a8f8038d/attachment.html>