Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of david_jencks@yahoo.com
 designates 98.138.91.74 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com;
	b=trF0eeOfUeLWnAcrcJlAIqBhPm32HjJkiukRBLtgOqYRddJ9wl9trPuj0YbNK1iIXh1apnQ8nu/dn0WM5m55kgQtr+gXT3Y/ggsGNhmLfyv3GRyMteSjzdGcNTTJYPBW4E5L6Os/KBH181RfP/zGSt/UgxQNNZdJhXVwDCexrvutYXZQVsvRENwleZDF2Ea76b2D8gDefJBdwirxnYav7udSN+ogyZW198cNEqgBIXoI4n394pL+Rtbnm9Wbf9ljOTUb34ptwyKjzvoZR4OhCZ1e0k4WThYll2mcQuwJtV5b3cTTbsyKGs837WmZXvl1paOEEtf9i2BHDxS0UQezdg==;
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: testing a service, mocking dependencies
From: David Jencks <david_jencks@yahoo.com.INVALID>
In-Reply-To: <D03E007A.FD7%konstantine.kougios@akqa.com>
Date: Tue, 16 Sep 2014 07:22:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDFF500A-7A09-45C0-A842-4BB430B38D18@yahoo.com>
References: <D03DFC11.FD3%konstantine.kougios@akqa.com>
 <CAMit8SqeyaoryJTpHFq1sO917tm3oXjo_mw4Kd+_vOLBpo5FCw@mail.gmail.com>
 <D03E007A.FD7%konstantine.kougios@akqa.com>
To: users@felix.apache.org

You don't provide enough information to know what you are doing, and I =
don't understand what you mean by a unit test.

If you are writing a DS component and using Felix DS annotations, note =
that the @Reference on a field without accessors results in byte code =
generation of accessor methods.  You might want to write them yourself.

Is your "unit test" running in a DS container? =20

If not, then you need to simulate the calls to the event =
(bind/updated/unbind) and lifecycle (activate/modified/deactivate) =
methods that the container will make in your unit test.  After all the =
"stop" methods (deactivate and unbind) are called, the container will =
discard the component instance.

If you are running in a DS container then register your B as a service =
and the container will take care of calling the (generated, with your =
current code)bind/unbiind methods.

LIke every other component framework that accesses apparently invisible =
members during runtime, DS calls setAccessible internally so it can =
access them.  The spec may support field injection in the future and it =
will be supported using setAccssible pretty much exactly as David  B. =
suggests.

david jencks

On Sep 16, 2014, at 6:59 AM, Konstantine Kougios =
<Konstantine.Kougios@akqa.com> wrote:

> Well, that=B9s similar to the forTesting factory I mention but with =
the
> drawback that the state of A is corrupted until the JVM terminates. By
> corrupted I mean that my mock will be part of A until either the jvm =
stops
> or something else injects a different thing to A.b. If the mock is set
> this way while running in-container tests, A state is corrupted.
>=20
>=20
> On 16/09/2014 14:56, "David Bosschaert" <david.bosschaert@gmail.com> =
wrote:
>=20
>> Why not set the field b in your object manually to the mock B for =
unit
>> testing?
>>=20
>> Just assign it to the field. If you insist on having it private you
>> can call 'Field.setAccessible(true)' in your unit test and assign it
>> using reflection...
>>=20
>> Best regards,
>>=20
>> David
>>=20
>> On 16 September 2014 14:39, Konstantine Kougios
>> <Konstantine.Kougios@akqa.com> wrote:
>>> Hi, say I got a service A, which has a
>>>=20
>>> @Reference private B b;
>>>=20
>>> Now I want to write a unit test and mock B, how can I inject the =
mocked
>>> dependency?
>>>=20
>>> Only reasonable thing I found so far is to have a static factory =
method
>>> on A, public static A forTesting(B b) { =8A }
>>>=20
>>> Thanks,
>>>=20
>>> Kostas
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>=20


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