Re: [easyb-users] looking for examples of easyb in the enterprise

[Rajiv Narula]

If you need a single tool that will work everywhere- easyB+Geb may not be it. I am no automation expert - but the fancy shrink-wrapped ones are going to appeal to big-wigs more.(wonder- if we work for same company ? ;) )

If you want a single automation architecture- it will probably need couple of tools and easyB +Geb\Selenium can be part of it- but ant deliver all

FWIW...

We are using easyB+groovy+selenium 

Project is managed via Gradle

Using Jenkins for Cont Delivery

Will be happy to share more

http://www.rajivnarula.com/blog/2012/01/12/def-test-new-bddmadeeasyseleniumeasybgroovy/

On Tue, Jun 4, 2013 at 7:57 PM, <markbc...@gmail.com> wrote:

I am looking for case studies / examples of the use of easyb + (Geb / whatever) in the enterprise. 

My organization would prefer to use a single tool that can test a wide range of environments.  Tools like HP Quality Center are very appealing to the executives, but I would prefer to use lighter weight, more focused, loosely coupled tool chains.  I can find some examples of Cucumber being used for different platforms, but I do not see anything like that for easyb.

Does anybody out there have any experience or examples of large enterprise adoption of easyb or use of easyb across multiple platforms? 

If it's just going to be a solution that only works for Java platform applications, web applications and web services, then that's probably not going to satisfy the enterprise architects.

Thanks;

--
You received this message because you are subscribed to the Google Groups "Easyb Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easyb-users...@googlegroups.com.
To post to this group, send email to easyb...@googlegroups.com.
Visit this group at http://groups.google.com/group/easyb-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
-Rajiv
www.rajivnarula.com

[markbc...@gmail.com]

On Tuesday, June 4, 2013 8:13:40 PM UTC-5, Rajiv Narula wrote:

If you need a single tool that will work everywhere- easyB+Geb may not be it.

I wasn't really expecting it to, which is why I wrote 'easyb + (Geb / whatever) ' in the original post. 

Since testing tends to be very platform specific, the test code in the braces for an easyb story/spec is going to be different for different realms.  For web applications, Geb looks very good because when combined with the PageObject pattern, it yields very readable code that is also very maintainable (= cost effective).

For Java GUI applications, the 'whatever' will be a Swing testing tool.  Similarly for batch programs ETL jobs perhaps plain old jUnit used as a functional test tool would probably work fine. For WebServices a WebService testing tool would be used.

What I really need to know though, is can we still use easyb for acceptance testing in development projects and integration/functional/regression testing for production candidates when those projects are not on the Java platform?  We have a fair bit of C/C++ on Linux and even some C++ on Qt.  I'm OK with the solution being inadequate for mainframe, which is being phased out, but if it can't be used sensibly with C and C++ programs, then we have a problem.

I know that Cucumber has versions for a number of different platforms with Gherkin being the common dialect between them, but I have not seen any examples of testing non Java platform applications with easyb and that's what I'm looking for.
 

I am no automation expert - but the fancy shrink-wrapped ones are going to appeal to big-wigs more.(wonder- if we work for same company ? ;) )

If you want a single automation architecture- it will probably need couple of tools and easyB +Geb\Selenium can be part of it- but ant deliver all

 

FWIW...

We are using easyB+groovy+selenium 

Project is managed via Gradle

 

Using Jenkins for Cont Delivery

Yes, we are also using Jenkins and it would be the top of the build stack that I would like to propose.  Along with the dashboard plugin and combined test results and code quality metrics, it could provide a very light weight and flexible build system that could also track project progress and product health.

Using Jira with GreenHopper for Story management and workflow as well as development issue management and workflow, a project specific Jenkins build with easyb could provide project completion and acceptance status after every build, probably using the easyb-reports-html generator.

The trick here is universality.  At the top level, we could use the same tools for all of our platforms.  I'm hoping that the divergence only needs to happen at the lower levels where implementation details rule and executives loose interest.  I'd like that divergence to occur below easyb.
 

Will be happy to share more

Thanks.