I am probably only showing my ignorance here, but is the cause of the
problems with using ThreadedRepeat and CombinatorialTest not in the
following code section from CombinatorialRun.cs (in TupleRunInvoker)?
public override Object Execute(Object o, IList args)
{
foreach (Object item in this.tuple)
args.Add(item);
object[] arguments = new object[args.Count];
args.CopyTo(arguments, 0);
this.method.Invoke(o, arguments);
args.Clear();
return null;
}
The above is not thread safe (or am I wrong?), causing the
Parameter error when Invoke is called in multi-threaded tests.
On Jun 28, 10:20 am, Jacques <[EMAIL PROTECTED]> wrote:
> I am referring to the topic of 1 Dec 2006.
>
> Re: MbUnit ThreadedRepeat and [CombinatorialTest]
>
> Was this issue resolved since? To me it seems that you can only use
> [ThreadedRepeat] with the [Test] attribute, and not with
> [CombinatorialTest] or the DataFixture (or others). I get the
> Parameter count error with these, but it works with the classic Test
> attribute. Is it suppose to work like this?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---
