I can give more info on how I used this stuff if you are interested.
-Fred
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dain
Sundstrom
Sent: Wednesday, December 11, 2002 12:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Testing EJB's
If y
If you want to test in JBoss, you will need to have JBoss running
somehow. Unless you are running on a very old machine, the JBoss start
up should be start fairly quickly (under 30 sec). I usually just leave
a JBoss instance running, and test over and over again.
-dain
On Wednesday, December
Thanks, Dain. At first, I was encouraged by your reply, so I checked
out the source, but it doesn't address my needs. At least, the branch
I checked out (3.0 and jboss-head) could not run the testsuite
successfully without first firing up JBoss.
I want to be able to test my CMP's in an in-memory
On Tue, Dec 10, 2002 at 03:23:31PM -0500, Jim Crossley wrote:
> The app I'm currently working on is very CRUD-ish; it does simple
> read/write maintenance on a bunch of related objects. I don't want the
> web tier to access the Entity beans directly -- this would violate the
> transactional req
On Tue, Dec 10, 2002 at 02:32:17PM -0600, Dain Sundstrom wrote:
> Jim,
>
> How do you think we test JBoss? Take a look at the CMP tests in the
> testsuite. We have an addon to JUnit that can deploy and undeploy
> applications. Also we have a tool that can run the tests on the server
> side
Craig
> -Original Message-
> From: Jim Crossley [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 10, 2002 3:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Testing EJB's
>
>
> These are good points, and I appreciate yours and others' prompt
> replies
having such problems is
greatly minimized.
Craig
> -Original Message-
> From: Igor Fedorenko [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 10, 2002 3:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Testing EJB's
>
>
> This aproach does not tes
Jim,
How do you think we test JBoss? Take a look at the CMP tests in the
testsuite. We have an addon to JUnit that can deploy and undeploy
applications. Also we have a tool that can run the tests on the server
side like (I wrote this to test local interfaces), but does not require
a servlet
These are good points, and I appreciate yours and others' prompt
replies. However, the solutions presented so far seem to force me to
complicate my object model to facilitate testing.
I agree that an app that is difficult to test probably suffers from poor
design, but web apps by their very na
This aproach does not test deployment descriptors. I've had quite a few
problems with missing ejb-ref, resource-ref, etc. What is especially bad
is that you do not know if your deployment descriptor has a problem
until you actually try to execute line of code that uses missing resource.
Demyano
Jim,
I currently do not unit test either Entity or Session Beans. Entity Beans
are trivial to write, and I trust that the application server will persist
them as advertised. To unit test Session Beans would require that they be
deployed. Since deployment complicates unit testing and complicated
Hi -
Not sure if I completely understand your question, but we use JUnitEE, which
runs as a servlet inside the container. It invokes your unit tests and
displays the results in HTML format. Very nice.
Personally, we always run tests on the remote interfaces of our EJBs so that
we can test the
Title: RE: [JBoss-user] Testing EJB's
My advice will be to expose the remote interface of the component, so that
you can test is with standard JUnit test cases.
Its easy and you test framework is simple.
But, you have to deploy your component to JBoss
-Original Message-
From
13 matches
Mail list logo
