Updates to NUnit 2.5

Discussion:

Charlie Poole

2008-06-16 19:14:21 UTC

Hi All,

Now that I'm back home, I can properly upload a number of changes
I made on my laptop while travelling.

So far, I have made the following changes:

1. The release is now 2.5 Alpha 3.

2. I have changed DataSourceAttribute to FactoryAttribute and it
may now appear on a property, field or method. Any of these may
be either static or instance members.

3. IParameterProvider.GetParametersFor(MethodInfo method) now
returns IEnumerable rather than IList.

4. The Test abstract class now has default implementations for
several properties that were previously abstract. One of the
Run() overloads has been removed.

I'll post further as more changes are made.

Charlie

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

Charlie Poole

2008-06-22 16:28:59 UTC

Permalink

More updates checked into CVS. All of this will be documented
for the release, but some of you may want an early heads-up,
especially if you are working on addins.

EXTENSIBILITY

The ParameterProviders extension point has been renamed
to TestCaseProviders. The interface that extensions must
implement is now ITestCaseProvider. Here's the definition:

public interface ITestCaseProvider
{
bool HasTestCasesFor(MethodInfo method);
IEnumerable GetTestCasesFor(MethodInfo method);
}

This is essentially the same as the IParameterProvider
interface in the first two alphas.

BUILT-IN PARAMETERIZED TESTS

NUnit currently has two built-in providers:
TestCaseParameterProvider for TestCaseAttribute and
TestCaseFactoryProvider for FactoryAttribute.

TestCaseParameterProvider will perform a number of
conversions in order to make the provided argument
compatible with method call.

TestCaseFactoryProvider can work with properties,
methods and fields that implement IEnumerable. For
static cases, use of an array is the simplest
approach. Either static or instance members may be
used. For methods takin a single ValueType argument,
the enumerator may return the bare argument rather
than an array with one member.

All of the above work at load time. For dynamic
test cases, provided at the instance of executin
the test and possibly varying from run to run, I
plan to add DynamicTest and DynamicTestCaseProvider.

OTHER STUFF

The RequiredAddinAttribute may be placed on the assembly,
on a class or on a method. If the named addin is not
loaded, the test or suite is NotRunnable and shows up
as red in the Gui.

Charlie

-----Original Message-----
Behalf Of Charlie Poole
Sent: Monday, June 16, 2008 12:14 PM
Subject: [nunit-developer] Updates to NUnit 2.5
Hi All,
Now that I'm back home, I can properly upload a number of
changes I made on my laptop while travelling.
1. The release is now 2.5 Alpha 3.
2. I have changed DataSourceAttribute to FactoryAttribute and
it may now appear on a property, field or method. Any of
these may be either static or instance members.
3. IParameterProvider.GetParametersFor(MethodInfo method) now
returns IEnumerable rather than IList.
4. The Test abstract class now has default implementations
for several properties that were previously abstract. One of the
Run() overloads has been removed.
I'll post further as more changes are made.
Charlie
--------------------------------------------------------------
-----------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for just about
anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

Charlie Poole

2008-06-24 21:59:48 UTC

Permalink

More updates for those following CVS - note that the attached
emails cover all the important changes since the Alpha 2 release,
and will be reflected in the next Alpha in a few weeks.

There is a major change to the Test hierarchy: TestCase doesn't
exist any longer. TestMethod inherits directly from Test now
and represents a Test implemented by a method. There could be
some further changes in this branch as well as for TestSuite,
TestFixture, etc.

All this is part of the move to parameterized tests, which
blurs the distinction between a suite and a case. I'm currently
using "test case" to refer to a single execution of a test with
one set of parameters, producing one result and the class names
will begin to reflect that.

NUnitTestCaseBuilder is now split in two, with the original
builder handling "regular" tests and ParameterizedTestCaseBuilder
handling parameterized tests. A new DynamicTestBuilder, which
recognizes DynamicTestAttribute and creates DynamicTests is

Charlie

-----Original Message-----
Behalf Of Charlie Poole
Sent: Sunday, June 22, 2008 9:29 AM
Subject: Re: [nunit-developer] Updates to NUnit 2.5
More updates checked into CVS. All of this will be documented
for the release, but some of you may want an early heads-up,
especially if you are working on addins.
EXTENSIBILITY
The ParameterProviders extension point has been renamed to
TestCaseProviders. The interface that extensions must
public interface ITestCaseProvider
{
bool HasTestCasesFor(MethodInfo method);
IEnumerable GetTestCasesFor(MethodInfo method);
}
This is essentially the same as the IParameterProvider
interface in the first two alphas.
BUILT-IN PARAMETERIZED TESTS
TestCaseParameterProvider for TestCaseAttribute and
TestCaseFactoryProvider for FactoryAttribute.
TestCaseParameterProvider will perform a number of
conversions in order to make the provided argument compatible
with method call.
TestCaseFactoryProvider can work with properties, methods and
fields that implement IEnumerable. For static cases, use of
an array is the simplest approach. Either static or instance
members may be used. For methods takin a single ValueType
argument, the enumerator may return the bare argument rather
than an array with one member.
All of the above work at load time. For dynamic test cases,
provided at the instance of executin the test and possibly
varying from run to run, I plan to add DynamicTest and
DynamicTestCaseProvider.
OTHER STUFF
The RequiredAddinAttribute may be placed on the assembly, on
a class or on a method. If the named addin is not loaded, the
test or suite is NotRunnable and shows up as red in the Gui.
Charlie

-----Original Message-----
Charlie Poole
Sent: Monday, June 16, 2008 12:14 PM
Subject: [nunit-developer] Updates to NUnit 2.5
Hi All,
Now that I'm back home, I can properly upload a number of changes I
made on my laptop while travelling.
1. The release is now 2.5 Alpha 3.
2. I have changed DataSourceAttribute to FactoryAttribute

and it may

now appear on a property, field or method. Any of these may

be either

static or instance members.
3. IParameterProvider.GetParametersFor(MethodInfo method)

now returns

IEnumerable rather than IList.
4. The Test abstract class now has default implementations

for several

properties that were previously abstract. One of the
Run() overloads has been removed.
I'll post further as more changes are made.
Charlie
--------------------------------------------------------------
-----------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for just about anything
Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

--------------------------------------------------------------
-----------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for just about
anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

Charlie Poole

2008-06-27 17:42:04 UTC

Permalink

Checked in a VS2008 build and blogged about it here:
http://nunit.org/blogs/?p=61

Charlie

and it may

now appear on a property, field or method. Any of these may

be either

static or instance members.
3. IParameterProvider.GetParametersFor(MethodInfo method)

now returns

IEnumerable rather than IList.
4. The Test abstract class now has default implementations

for several

Charlie Poole

2008-07-01 02:11:42 UTC

Permalink

Hi All,

Latest checkins include new version numbering scheme for
NUnit and generic parameterized test methods.

The NUnit 2.5 Alphas were both numbered 2.5.0.0, which could
be confusing. From now the release builds will carry a build
number in the fourth position, of the form yddd, where y is
the last digit of the year and ddd is the day number within
the year. So, if 2.5 were released today, it would be
2.5.0.8182.

Parameterized test methods can now be generic and NUnit will
provide an appropriate specialization of the method for each
set of parameters provided. This is actually of limited
utility by itself, but will be more useful in combination with
the support for generic fixtures I'm currently working on.

Charlie

-----Original Message-----
Behalf Of Charlie Poole
Sent: Friday, June 27, 2008 10:42 AM
Subject: Re: [nunit-developer] Updates to NUnit 2.5
http://nunit.org/blogs/?p=61
Charlie

-----Original Message-----
Charlie Poole
Sent: Sunday, June 22, 2008 9:29 AM
Subject: Re: [nunit-developer] Updates to NUnit 2.5
More updates checked into CVS. All of this will be

documented for the

release, but some of you may want an early heads-up,

especially if you

are working on addins.
EXTENSIBILITY
The ParameterProviders extension point has been renamed to
TestCaseProviders. The interface that extensions must

implement is now

public interface ITestCaseProvider
{
bool HasTestCasesFor(MethodInfo method);
IEnumerable GetTestCasesFor(MethodInfo method);
}
This is essentially the same as the IParameterProvider interface in
the first two alphas.
BUILT-IN PARAMETERIZED TESTS
TestCaseParameterProvider for TestCaseAttribute and
TestCaseFactoryProvider for FactoryAttribute.
TestCaseParameterProvider will perform a number of conversions in
order to make the provided argument compatible with method call.
TestCaseFactoryProvider can work with properties, methods

and fields

that implement IEnumerable. For static cases, use of an

array is the

simplest approach. Either static or instance members may be

used. For

methods takin a single ValueType argument, the enumerator

may return

the bare argument rather than an array with one member.
All of the above work at load time. For dynamic test cases,

provided

at the instance of executin the test and possibly varying

from run to

run, I plan to add DynamicTest and DynamicTestCaseProvider.
OTHER STUFF
The RequiredAddinAttribute may be placed on the assembly,

on a class

or on a method. If the named addin is not loaded, the test

or suite is

NotRunnable and shows up as red in the Gui.
Charlie

-----Original Message-----

Behalf Of

Charlie Poole
Sent: Monday, June 16, 2008 12:14 PM
Subject: [nunit-developer] Updates to NUnit 2.5
Hi All,
Now that I'm back home, I can properly upload a number of

changes I

made on my laptop while travelling.
1. The release is now 2.5 Alpha 3.
2. I have changed DataSourceAttribute to FactoryAttribute

and it may

now appear on a property, field or method. Any of these may

be either

static or instance members.
3. IParameterProvider.GetParametersFor(MethodInfo method)

now returns

IEnumerable rather than IList.
4. The Test abstract class now has default implementations

for several

about anything

Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

--------------------------------------------------------------
-----------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for just about anything
Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

Charlie Poole

2008-07-03 01:17:19 UTC

Permalink

[NOTE: I'm now updating the release notes for the 2.5
release when I make these posts, so they no longer need
to be cumulative. See http://nunit.org/?p=releaseNotes&r=2.5]

Latest CVS updates:

Simone Busoli contributed an IsOrdered constraint and
assertion for use on collections.

TestFixtures may now be generic and have the specific
types to use as type arguments provided on the TestFixture
attribute. You can have multiple TestFixture attributes
on one class. See my blog for an example: http://nunit.org/blogs.

Charlie

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

Kelly Anderson

2008-07-03 16:25:26 UTC

Permalink

Things have been crazy busy lately, but I'm still very interested in
2.5 and 3.0!

When do you anticipate having a third alpha of 2.5 for download rather
than the CVS?

-Kelly

On Wed, Jul 2, 2008 at 7:17 PM, Charlie Poole

Post by Charlie Poole
[NOTE: I'm now updating the release notes for the 2.5
release when I make these posts, so they no longer need
to be cumulative. See http://nunit.org/?p=releaseNotes&r=2.5]
Simone Busoli contributed an IsOrdered constraint and
assertion for use on collections.
TestFixtures may now be generic and have the specific
types to use as type arguments provided on the TestFixture
attribute. You can have multiple TestFixture attributes
on one class. See my blog for an example: http://nunit.org/blogs.
Charlie
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

Charlie Poole

2008-07-03 16:35:56 UTC

Permalink

"Soon" :-)

Seriously, I'll evaluate today or tomorrow whether to release with
what I have or to go into next week. As it looks now, the difference
will probably be whether parameterized fixtures make it into the
release.

Charlie

-----Original Message-----
Behalf Of Kelly Anderson
Sent: Thursday, July 03, 2008 9:25 AM
Subject: Re: [nunit-developer] Updates to NUnit 2.5
Things have been crazy busy lately, but I'm still very interested in
2.5 and 3.0!
When do you anticipate having a third alpha of 2.5 for
download rather than the CVS?
-Kelly
On Wed, Jul 2, 2008 at 7:17 PM, Charlie Poole

Post by Charlie Poole
[NOTE: I'm now updating the release notes for the 2.5

release when I

Post by Charlie Poole
make these posts, so they no longer need to be cumulative. See
http://nunit.org/?p=releaseNotes&r=2.5]
Simone Busoli contributed an IsOrdered constraint and assertion for
use on collections.
TestFixtures may now be generic and have the specific types

to use as

Post by Charlie Poole
type arguments provided on the TestFixture attribute. You can have
multiple TestFixture attributes on one class. See my blog for an
example: http://nunit.org/blogs.
Charlie

----------------------------------------------------------------------

Post by Charlie Poole
--- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open

source project,

Post by Charlie Poole
along with a healthy diet, reduces your potential for

chronic lameness

Post by Charlie Poole
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

--------------------------------------------------------------
-----------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source
project, along with a healthy diet, reduces your potential
for chronic lameness and boredom. Vote Now at
http://www.sourceforge.net/community/cca08
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

Charlie Poole

2008-07-04 02:27:27 UTC

Permalink

Hi All,

Latest checkin finishes work on TestCaseFactories, which are
methods, properties or fields that provide test cases to a
parameterized test. There's one outstanding question I could
use some ideas on - see the end of this note.

TestCaseFactoryAttribute is an optional attribute that can
be used to mark these factories. If used, it should specify
the types of the arguments provided... e.g.:
[TestCaseFactory(typeof(int), typeof(int), typeof(string))]

FactoryAttribute is used on the parameterized test itself and
has the following forms:
[Factory]
[Factory(Type factoryType)]
[Factory(string factoryNames)]
[Factory(Type factoryType, string factoryNames)]

factoryType is the type of the object that holds the factory,
defaulting to the same class as the test.

factoryName is the name of the method, property or field that
serves as a factory - or several names separated by commas. It
defaults to "find all compatible test factories in the type".

If you are looking for compatible test factories, that's when
you need to mark them with the TestCaseFactoryAttribute. Compatible
means that the types match the argumets of the test method.

Here's the question: I'm still not happy with "Factory" to
identify indicate that factories should be used, especially
the form without any arguments. MbUnit uses "UsesFactories"
for a similar situation, so that might work. Any ideas?
Note that we will want to use the same attribute on
individual arguments as well as on methods.

Charlie

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

Charlie Poole

2008-07-04 19:42:08 UTC

Permalink

I just updated the online documentation to match what's in CVS.
See for example:
http://nunit.org/?p=testCase&r=2.5
http://nunit.org/?p=factory&r=2.5
http://nunit.org/?p=testCaseFactory&r=2.5

I'm still looking for suggestions regarding renaming FactoryAttribute.

Charlie

-----Original Message-----
Behalf Of Charlie Poole
Sent: Thursday, July 03, 2008 7:27 PM
Subject: Re: [nunit-developer] Updates to NUnit 2.5
Hi All,
Latest checkin finishes work on TestCaseFactories, which are
methods, properties or fields that provide test cases to a
parameterized test. There's one outstanding question I could
use some ideas on - see the end of this note.
TestCaseFactoryAttribute is an optional attribute that can be
used to mark these factories. If used, it should specify the
[TestCaseFactory(typeof(int), typeof(int), typeof(string))]
FactoryAttribute is used on the parameterized test itself and
[Factory]
[Factory(Type factoryType)]
[Factory(string factoryNames)]
[Factory(Type factoryType, string factoryNames)]
factoryType is the type of the object that holds the factory,
defaulting to the same class as the test.
factoryName is the name of the method, property or field that
serves as a factory - or several names separated by commas.
It defaults to "find all compatible test factories in the type".
If you are looking for compatible test factories, that's when
you need to mark them with the TestCaseFactoryAttribute.
Compatible means that the types match the argumets of the test method.
Here's the question: I'm still not happy with "Factory" to
identify indicate that factories should be used, especially
the form without any arguments. MbUnit uses "UsesFactories"
for a similar situation, so that might work. Any ideas?
Note that we will want to use the same attribute on
individual arguments as well as on methods.
Charlie
--------------------------------------------------------------
-----------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source
project, along with a healthy diet, reduces your potential
for chronic lameness and boredom. Vote Now at
http://www.sourceforge.net/community/cca08
_______________________________________________
nunit-developer mailing list
https://lists.sourceforge.net/lists/listinfo/nunit-developer

Olof Bjarnason

2008-07-04 20:26:46 UTC

Permalink

What about "Source"? Or maybe that's already taken?

Post by Charlie Poole
I just updated the online documentation to match what's in CVS.
http://nunit.org/?p=testCase&r=2.5
http://nunit.org/?p=factory&r=2.5
http://nunit.org/?p=testCaseFactory&r=2.5
I'm still looking for suggestions regarding renaming FactoryAttribute.
Charlie

Charlie Poole

2008-07-04 20:47:02 UTC

Permalink

Sounds like a good possibility, although it seems to share
with "Factory" the deficiency of not making much sense when
used without arguments.

Maybe I should leave the attribute off in that case...

What if
[Test]
public void Method(int x, int y) { ... }
automatically searched for a factory within the class?

Would that lead to confusion?

Charlie

-----Original Message-----
Behalf Of Olof Bjarnason
Sent: Friday, July 04, 2008 1:27 PM
To: Charlie Poole
Subject: Re: [nunit-developer] Updates to NUnit 2.5
What about "Source"? Or maybe that's already taken?

FactoryAttribute.

Post by Charlie Poole
Charlie

-----Original Message-----

Behalf Of