Mailing-List: contact users-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tapestry users" <users@tapestry.apache.org>
Received-SPF: pass (athena.apache.org: domain of hlship@gmail.com designates
 64.233.170.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=Phw74Y0uCbfF1ZLZoaleop9xs3WeSh8VohVo5BqsVi4ULlVrLRdX8QEvc1AyROCsml
         URmRO659iVKAsp3Wsr29wG4rqLgFCRDp1loLaHpd1APxReIhUccyAmDBza/fapraCLT7
         hlcXX052g6RXRi8pFcwPe3uVHZdJKXspbqnqo=
Message-ID: <ecd0e3310812041223x177effd1y3e8c6f00b5dc136@mail.gmail.com>
Date: Thu, 4 Dec 2008 12:23:27 -0800
From: "Howard Lewis Ship" <hlship@gmail.com>
To: "Tapestry users" <users@tapestry.apache.org>
Subject: Re: IoC registry survives between JUnit tests?
In-Reply-To: <27A88558-770B-4546-9AEB-4BCF43F617B0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20828078.post@talk.nabble.com>
	 <27A88558-770B-4546-9AEB-4BCF43F617B0@gmail.com>

I use a mix of techniques, using a lot of mocks for true unit tests,
but also a lot of integration tests.

I'm not sure what CEG has actually seen here; Registry.shutdown() is
very dramatic, it tears apart the registry (releasing almost
everything to the GC) and informs all of the proxies to shutdown as
well.  Could he just be missing the re-creation of the services in
later tests ... Registry startup is very, very fast once all the
underlying classes are instantiated.

On Thu, Dec 4, 2008 at 12:04 PM, Christian Edward Gruber
<christianedwardgruber@gmail.com> wrote:
> FYI, in general, you shouldn't be using the container in your tests, unless
> you're testing the wiring itself.  You should be creating the
> component/service under test, and constructing it with fakes.  This isn't
> absolute but there is a lot more effort/configuration/overhead if you want
> to use the container infrastructure in your unit test, and you start to have
> subtle interactions that might potentially make it more of an integration
> test.  You risk testing more than one thing at a time.
>
> Christian
>
> On 4-Dec-08, at 01:28 , Stephan Schwab wrote:
>
>>
>> Hi!
>>
>> I have several JUnit tests that instantiate
>> org.apache.tapestry5.ioc.Registry via the RegistryBuilder before tests
>> run.
>> Now I'm observing that services registered in one test are still available
>> in other tests although I did call registry.shutdown(). My test runner
>> does
>> not fork a new JVM.
>>
>> Calling registry.shutdown() should cause everything to vanish. Is there
>> anything that causes one-registry-per-JVM?
>>
>> Stephan
>>
>>
>>
>> -----
>> --
>> http://www.caimito.net - Caimito One Team - Agile Collaboration and
>> Planning
>> tool
>> http://www.stephan-schwab.com - Personal blog
>> http://code.google.com/p/tapestry-sesame - Authentication extension for
>> Tapestry 5
>>
>> --
>> View this message in context:
>> http://www.nabble.com/IoC-registry-survives-between-JUnit-tests--tp20828078p20828078.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org