Charlie Poole
2008-08-14 01:30:49 UTC
Hi All,
As a result of a bug report, I have come to realize that the
NUnit PropertyAttribute exposes NUnit to failures. The
value of a property is permitted to be any arbitary object,
which may not be serializable and - even if it is - may
be of a type defined in an assembly that NUnit doesn't
know about.
That's because test properties make it all the way back to
the Gui, where they are displayed.
My inclination is to allow only string values or possibly
numerics. What do you all prefer?
Charlie
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
As a result of a bug report, I have come to realize that the
NUnit PropertyAttribute exposes NUnit to failures. The
value of a property is permitted to be any arbitary object,
which may not be serializable and - even if it is - may
be of a type defined in an assembly that NUnit doesn't
know about.
That's because test properties make it all the way back to
the Gui, where they are displayed.
My inclination is to allow only string values or possibly
numerics. What do you all prefer?
Charlie
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/