• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

The use of Jython in TestMaker

 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Frank,

While I certainly see why you've chosen to use Jython as the scripting language of choice in TestMaker, I'm wondering if you're at all worried about the future of Jython? It seems that the development of Jython has effectively stopped (with the last alpha release dated July 2003).

Talking of scripting languages, I believe the competitive matrix on your site has incorrect information; LoadRunner supports both C and Java for programming the test scripts. I also wouldn't call these "proprietary scripting languages".
 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mike Clark uses Groovy to do some build and test automation in his "Pragmatic Project Automation." Any comment about the relative merits of Jython and Groovy?
 
author
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Lasse: Jython's viability as a language has been in question for a long time. It seems to be a recurring theme. I chose Jython as the TestMaker scripting language two years ago and I've been happy with the choice. The Jython project runs two email lists (jython-users@lists.sourceforge.net and jython-dev@lists.sourceforge.net). All of the questions I have posed there have been responded to by other users and the maintainers (Samuele Pedrone, Clark Updike, and others.

The developers are working on Jython 2.2 that will incorporate several changes that have happened on the Python side over the years.

The most impressive thing to me about Jython is its stability. I have run complex scalability tests of Service Oriented Architecture (SOA) with up to 20,000 concurrently running test agents written in Jython. Jython is solid.

Groovy looks just that: it's groovy. I like the fact that Groovy compiles into Java byte codes. This is VERY important to the Java community as it puts Java on a better competitive footing with .NET's ability to run multiple languages through their VM. Please read my blog about Java and scripting. The biggest problem for Jython and Groovy is Sun's reluctance to endorse scripting and to support it.

-Frank
 
Frank Cohen
author
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Talking of scripting languages, I believe the competitive matrix on your site has incorrect information; LoadRunner supports both C and Java for programming the test scripts. I also wouldn't call these "proprietary scripting languages".



I'm ready to take down that competitive matrix. At one time I thought Mercury and PushToTest were competitng with each other. With the past 3 year's experience working with software developers, QA technicians, and IT managers I see that the tools we use to test and monitor systems are less important than the techniques and best practices. It's like the early days of desktop publishing, the publishing software let everyone choose crappy fonts and bad layouts. I think the same is true about testing tools.

I recently met with Mercury Interactive's management to talk about software developers, testing, and open-source. I am now looking into how Load Runner can be used by developers to turn unit tests into scalability and performance tests. I can envision a jUnit2LoadRunner utility, for example. I'd love to hear your feedback on these thoughts.

-Frank
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Frank Cohen:
I recently met with Mercury Interactive's management to talk about software developers, testing, and open-source. I am now looking into how Load Runner can be used by developers to turn unit tests into scalability and performance tests. I can envision a jUnit2LoadRunner utility, for example. I'd love to hear your feedback on these thoughts.


Would that be a bit like Mike Clark's JUnitPerf but only with "commercial-grade" stats and diagrams?

Anyway, I'm afraid I'm too hostile towards LoadRunner to be able to provide useful feedback. It's certainly one of the best tools available but I wouldn't want to be the one who has to use it...
 
drifter
Posts: 1364
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Frank Cohen:

...
I recently met with Mercury Interactive's management to talk about software developers, testing, and open-source. I am now looking into how Load Runner can be used by developers to turn unit tests into scalability and performance tests. I can envision a jUnit2LoadRunner utility, for example. I'd love to hear your feedback on these thoughts.

-Frank



Is part of the intent here to get Developers and QA/Testers to work together? Based on other comments of yours about troika or synergy when working together instead of alone I thought you might be. Developers create scalability/performance tests that QA (or perhaps even the managers you refer to?) can use?

I have mixed feelings about that. I can see great potential for synergy as well as pitfalls. Pitfall - QA tests exactly what the developers think needs testing. Synergy - QA says hey these are great, do you have a test that looks at xyz and developer runs off to create it. Synergy - QA and their management can relate to load runner more readily than something like JMeter or JUnitPerf.
reply
    Bookmark Topic Watch Topic
  • New Topic