classtester Work Item Rss Feed

COMMENTED ISSUE: Add support for Abstract Types and Interfaces to the TypeFactory

furie — Thu, 07 Feb 2008 15:28:30 GMT

Use a mock repository to add support for abstract types (abstract classes and interfaces) to the TypeFactory
Comments: ** Comment from web user: furie **

This can be done now by extending the TypeFactory an instance of it to a tester constructor.
using Castle.Core.Interceptor;
using Castle.DynamicProxy;
public class MyTypeFactory : TypeFactory
{
static ProxyGenerator proxyGenerator = new ProxyGenerator();
public override object CreateRandomValue(Type type)
{
if (type.IsInterface)
return proxyGenerator.CreateInterfaceProxyWithoutTarget(type, new StandardInterceptor());
return base.CreateRandomValue(type);
}
public override bool CanCreateInstance(Type type)
{
bool result = base.CanCreateInstance(type);
if (!result)
result = type.IsInterface && !type.IsGenericTypeDefinition;
retur result;
}

COMMENTED ISSUE: PropertyChecker to optionally test properties throw ArgumentNullException when setting null value

furie — Thu, 07 Feb 2008 15:16:59 GMT

Often a precondition of a property is that the value set is non null and therefore the property should throw an ArgumentNullExtension. Would be good to switch this checking on at class level. Also optionally checking string.Empty throws would be great also.
Comments: ** Comment from web user: furie **

Actually I think this would be better implemented as a seperate 'NullParam' tester that tested Constructors, Properties, and Methods.

CREATED ISSUE: PropertyChecker to optionally test properties throw ArgumentNullException when setting null value

furie — Thu, 07 Feb 2008 11:12:34 GMT

COMMENTED ISSUE: Add support for Abstract Types and Interfaces to the TypeFactory

furie — Thu, 07 Feb 2008 10:59:53 GMT

Use a mock repository to add support for abstract types (abstract classes and interfaces) to the TypeFactory
Comments: ** Comment from web user: furie **

Consider using Castle DynamicProxy 2 to create an instance of an abstract class. It's lightweight, quick and simple. RhinoMocks uses it to create its mocks.

CREATED ISSUE: Strongly signed assemblies

igorbrejc — Wed, 30 Jan 2008 08:18:51 GMT

Hello,

Thanks for a great tool and a great idea. The only thing I really miss is being able to use the library in a strongly signed test projects. Would it be possible for you to include this in the next release?

Best regards,
Igor

COMMENTED ISSUE: Compare two provided objects instead of comparing randomly generated value

Jericho — Fri, 11 Jan 2008 17:14:27 GMT

Comparing randomly genrated values is great for detecting bugs where a public property uses the wrong private field. Another test that would also be very useful is to compare all the properties of two provided objects. What I'm envisioning is something like this (this is only psendo-code):

[TestMethod]
public void TestPerson()
{
Person p1 = new Person();
p1.Name = "Bob Smith";
string personId = MyDAL.Save(p1);
Person p2 = MyDAL.Fetch(personId);
PropertyTester tester = new PropertyTester(p1, p2);
tester.TestProperties();
}
Comments: ** Comment from web user: Jericho **

I just submitted a patch with the code for a "PropertyComparer" class that will compare all the properties on two objects to make sure that the values are the same.

CLOSED ISSUE: Add support for creation of Arrays to TypeFactory

molmorg — Wed, 09 Jan 2008 17:31:08 GMT

TypeFactory can't currently create arrays (e.g. object[])

CREATED ISSUE: Compare two provided objects instead of comparing randomly generated value

Jericho — Mon, 07 Jan 2008 16:14:48 GMT

CREATED ISSUE: Exclude class property when testing Assembly

Jericho — Mon, 07 Jan 2008 16:05:18 GMT

The Assembly tester currently allows to exclude an entire namespace or an entire class but it would be great to also be able to exclude a specific property of a specific class. For example:

[code]
[Test]
public void AssemblyTester_PassWithExclusions()
{
AssemblyTester tester = new AssemblyTester("ExampleAssembly");
tester.Exclusions.AddProperty("ExampleAssembly.SomeNamespace.SomeClass", "PropertyName");
tester.TestAssembly(true, true);
}
[/code]

CREATED ISSUE: Improved error reporting from AssemblyTester

molmorg — Fri, 04 Jan 2008 14:40:18 GMT

Currently, because the AssemblyTester aggregates errors there it can be difficult to trace back what went wrong and there is no callstack

CREATED ISSUE: Add support for creation of Arrays to TypeFactory

molmorg — Fri, 04 Jan 2008 14:39:12 GMT

TypeFactory can't currently create arrays (e.g. object[])

CREATED ISSUE: Make the TypeFactory provider based

molmorg — Fri, 04 Jan 2008 14:11:34 GMT

Change the way the TypeFactory is referenced to make it pluggable and extendable so I can provide my own TypeFactory or extend the existing one.

CREATED ISSUE: Add support for creating types with non-default constructors to the TypeFactory

molmorg — Fri, 04 Jan 2008 13:02:34 GMT

Make the TypeFactory support types with non default constructors by using the TypeFactory to create the types required by the constructor.

CREATED ISSUE: Add support for Abstract Types and Interfaces to the TypeFactory

molmorg — Fri, 04 Jan 2008 13:00:51 GMT

Use a mock repository to add support for abstract types (abstract classes and interfaces) to the TypeFactory

CLOSED ISSUE: Remove Code Duplication from TestConstructors and TryCreateInstanstanceFromConstructor

molmorg — Thu, 03 Jan 2008 14:45:29 GMT

There is a huge body of code that's almost identical in the ConstructorTester.TestConstructors method and the AssemblyTester.TryCreateInstanstanceFromConstructor method. This should probably be factored out into the new TypeFactory.

CLOSED FEATURE: Ability to ignore constructors

molmorg — Thu, 03 Jan 2008 14:45:21 GMT

Ability to specify Constructors to be ignored as part of the TestConstructors method.

This would probably be require a change to an instance based method rather than a static one. For example

ConstructorTester tester = new ConstructorTester(typeof(MyClass));
// specify the signature of the constructor to ignore - IgnoreConstructor(params Type types);
tester.IgnoreConstructor(typeof(string), typeof(bool), typeof());
tester.Test();

For consistency we should probably change the ClassTester's class name to PropertyTester (but keep the ClassTester [inherit from PropertyTester] and mark obsolete to remain backwards compatible).

CLOSED FEATURE: Create AssemblyTester

molmorg — Thu, 03 Jan 2008 14:41:04 GMT

Design an approach to automate testing all properties and all constructors within an assembly.

Might be nice to have some exclusions - just some ideas here

AssemblyTester tester = new AssemblyTester(TODO - decide how best to specify an assembly);
tester.Exclusions.Add("YourNamespace.YourClass");
tester.Exclusions.Add(typeof(YourClass));
// second parameter could specify whether to exclude sub namespaces
tester.Exclusions.AddNamespace("YourNamespace", true);

// probably better to have separate methods so you don't have to do both if you don't want to - could always have an extra method that supports both
tester.TestProperties();
tester.TestConstructors();

CREATED ISSUE: Remove Code Duplication from TestConstructors and TryCreateInstanstanceFromConstructor

molmorg — Fri, 17 Aug 2007 09:39:37 GMT

CREATED FEATURE: Create AssemblyTester

molmorg — Fri, 10 Aug 2007 13:54:34 GMT

CREATED FEATURE: Ability to ignore constructors

molmorg — Fri, 10 Aug 2007 13:38:52 GMT