Re: Re: Re: And now write 100 times: "I'll automate our test-environment"

You could implement a similar framework for Java testing in Perl using Inline::Java within the test scripts to access the java classes (use STUDY or AUTOSTUDY options) Then you get all the power and simplicity of the Perl testing framework but can run the tests against Java Classes. You could also write some tests in Java and some in Perl as you desire. Given the far more strongly typed nature of Java you could stub up all sorts of 'standard' tests automatically. Just a thought.

cheers

tachyon

Comment on Re: Re: Re: And now write 100 times: "I'll automate our test-environment"

Replies are listed 'Best First'.
Re^4: And now write 100 times: "I'll automate our test-environment" by adrianh (Chancellor) on May 13, 2004 at 09:53 UTC
You could implement a similar framework for Java testing in Perl using Inline::Java within the test scripts to access the java classes (use STUDY or AUTOSTUDY options) Then you get all the power and simplicity of the Perl testing framework but can run the tests against Java Classes. I have to admit that if the application is mostly Java I would skip Perl and use JUnit and FIT for testing. I've found them a much better fit for Java based applications. Leveraging Java into Perl's testing framework doesn't really buy you much for a Java application, and JUnit is integrated into pretty much all of the popular Java IDEs. That said, it can sometimes be useful to use Test::Harness to bring the test suites of several different languages components together in a single reporting framework. Even then I'd probably be more inclined to use Inline::Java to run a JUnit test suite rather than move the tests into Perl.	[reply]

Replies are listed 'Best First'.

Re^4: And now write 100 times: "I'll automate our test-environment"
by adrianh (Chancellor) on May 13, 2004 at 09:53 UTC

You could implement a similar framework for Java testing in Perl using Inline::Java within the test scripts to access the java classes (use STUDY or AUTOSTUDY options) Then you get all the power and simplicity of the Perl testing framework but can run the tests against Java Classes.

I have to admit that if the application is mostly Java I would skip Perl and use JUnit and FIT for testing. I've found them a much better fit for Java based applications.

Leveraging Java into Perl's testing framework doesn't really buy you much for a Java application, and JUnit is integrated into pretty much all of the popular Java IDEs.

That said, it can sometimes be useful to use Test::Harness to bring the test suites of several different languages components together in a single reporting framework. Even then I'd probably be more inclined to use Inline::Java to run a JUnit test suite rather than move the tests into Perl.

[reply]