In fact, the TestContext is a temporary object, created each time it
is needed. So storing the randomizer in the TestContext would probably
be inefficient.

I suggest you use a property that directly accesses the cache of
Randomizers, using Randomizer.GetRandomizer(MemberInfo member). You
would have to get the methodinfo for the current test, most-likely
throwing an exception if the property was called from within a setup
method rather than a test, and use that as your argument to
GetRandomizer. A randomizer will be created and cached if it doesn't
already exist.

If this later proves inefficient, the same code could be moved to the
TestExecutionContext, which is referenced by the TestContext, but I
wouldn't be too quick to "optimize" this if I were you.

Charlie



On Tue, Feb 19, 2013 at 2:00 PM, Wes Cutting <email address hidden> wrote:
> I'm working in nunitlite.
>
>
> On Tue, Feb 19, 2013 at 2:40 PM, Charlie Poole <email address hidden> wrote:
>
>> It lasts only while the test itself is running. I can tell you what
>> files to look at if you tell me whether you are first working on
>> nunitlite or nunit-3.0.
>>
>> Charlie
>>
>> On Tue, Feb 19, 2013 at 1:14 PM, Wes Cutting <email address hidden>
>> wrote:
>> > Charlie,
>> >
>> > What is the lifecycle of the TestContext? I'm wondering when it is first
>> > created so I know when I can start manipulating it in order to add the
>> > randomizer.
>> >
>> > Thanks,
>> > Wes
>> >
>> >
>> > On Wed, Feb 13, 2013 at 5:10 PM, Charlie Poole <email address hidden>
>> wrote:
>> >
>> >> That sounds sensible to me. A lot of my classes start out as is-a and
>> >> later migrate to has-a for similar reasons.
>> >>
>> >> Charlie
>> >>
>> >> On Wed, Feb 13, 2013 at 2:19 PM, Wes Cutting <email address hidden>
>> >> wrote:
>> >> > We modified the relationship between Randomizer and Random from 'is-a'
>> >> > to 'has-a' in order to delay the construction of the backing Random.
>> >> > This allows us to intercept the seed used to create the Random, and
>> save
>> >> > it into a field which can be queried when writing the results of the
>> >> > test to the XML. All currently used public facing Random methods have
>> >> > had their appropriate wrapper methods added to Randomizer in order to
>> >> > preserve the functional contract; the solution still builds.
>> >> >
>> >> > Is this an acceptable solution for accessing the seed of the
>> Randomizer?
>> >> > The goal here was to expose the seed so testers can store that value
>> and
>> >> > pass it in for rerunning test identically. If so we will proceed with
>> >> > exposing the Randomizer to the testers in the Test Context.
>> >> >
>> >> > --
>> >> > You received this bug notification because you are subscribed to
>> >> > NUnitLite.
>> >> > https://bugs.launchpad.net/bugs/1111834
>> >> >
>> >> > Title:
>> >> >   Expose Random Object as part of the test context
>> >> >
>> >> > To manage notifications about this bug go to:
>> >> > https://bugs.launchpad.net/nunit-3.0/+bug/1111834/+subscriptions
>> >>
>> >> --
>> >> You received this bug notification because you are a bug assignee.
>> >> https://bugs.launchpad.net/bugs/1111834
>> >>
>> >> Title:
>> >>   Expose Random Object as part of the test context
>> >>
>> >> Status in NUnit Test Framework:
>> >>   Triaged
>> >> Status in NUnitLite Testing Framework:
>> >>   Triaged
>> >>
>> >> Bug description:
>> >>   When you have a test that needs to generate randomness but the random
>> >>   attribute is not sufficient, there is no way to make sure that the
>> >>   same random number is used across multiple test executions. In order
>> >>   to fix this it would be ideal to expose the already existing Random
>> >>   generator that is part of each test case on the context.
>> >>
>> >> To manage notifications about this bug go to:
>> >> https://bugs.launchpad.net/nunit-3.0/+bug/1111834/+subscriptions
>> >>
>> >
>> > --
>> > You received this bug notification because you are subscribed to
>> > NUnitLite.
>> > https://bugs.launchpad.net/bugs/1111834
>> >
>> > Title:
>> >   Expose Random Object as part of the test context
>> >
>> > To manage notifications about this bug go to:
>> > https://bugs.launchpad.net/nunit-3.0/+bug/1111834/+subscriptions
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> https://bugs.launchpad.net/bugs/1111834
>>
>> Title:
>>   Expose Random Object as part of the test context
>>
>> Status in NUnit Test Framework:
>>   Triaged
>> Status in NUnitLite Testing Framework:
>>   Triaged
>>
>> Bug description:
>>   When you have a test that needs to generate randomness but the random
>>   attribute is not sufficient, there is no way to make sure that the
>>   same random number is used across multiple test executions. In order
>>   to fix this it would be ideal to expose the already existing Random
>>   generator that is part of each test case on the context.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunit-3.0/+bug/1111834/+subscriptions
>>
>
> --
> You received this bug notification because you are subscribed to
> NUnitLite.
> https://bugs.launchpad.net/bugs/1111834
>
> Title:
>   Expose Random Object as part of the test context
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunit-3.0/+bug/1111834/+subscriptions