search

phuccaoca123 / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Assert exceptions are not serialized properly #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When you execute some test code in another AppDomain and get an exception,
this exception's message doesn't go through because of improper
(de)serialization. A typical example is NotEqualAssertionException: its
expectedMessage private variable doesn't go through the domain boundary and
is lost, so we can't see the stuff we usually see (like, "Equal assertion
failed: [[0]]!=[[1]]") and have to manually attach a descriptive message.

Original issue reported on code.google.com by uluhonol...@gmail.com on 20 Sep 2007 at 8:56

GoogleCodeExporter commented 9 years ago

Original comment by jeff.br...@gmail.com on 25 Sep 2007 at 2:19

GoogleCodeExporter commented 9 years ago 
Obsolete

Original comment by Yann.Tre...@gmail.com on 17 Jul 2010 at 8:17

GoogleCodeExporter commented 9 years ago 
Rest in peace

Original comment by uluhonol...@gmail.com on 17 Jul 2010 at 12:02

GoogleCodeExporter commented 9 years ago 
:)

Sorry for the pain. I have discarded all the issues of v2.4 because nobody 
maintains the code base anymore. I recommend to migrate to Gallio/MbUnit v3.1 
or v3.2 if not done already.

Regards,
Yann.

Original comment by Yann.Tre...@gmail.com on 18 Jul 2010 at 12:40

GoogleCodeExporter commented 9 years ago 
No pain at all, I've migrated ages ago. I was just surprised to discover this 
in my mailbox after I had completely forgotten about it. Couldn't resist ;)

ulu

Original comment by uluhonol...@gmail.com on 18 Jul 2010 at 12:45