Graeme Geldenhuys ha scritto:
> Here is the backtrace. I removed all other Assert tests, so only the
> one that causes the problem is executed.
>
> What is strange though, is that I created a new test that only creates
> the object and then tests the ObjectState. It it works, but all the
> other
Here is the backtrace. I removed all other Assert tests, so only the
one that causes the problem is executed.
What is strange though, is that I created a new test that only creates
the object and then tests the ObjectState. It it works, but all the
other actual tests don't. I hate such problems
Graeme Geldenhuys schreef:
Oh, I forgot to mention. If the ObjectStates match, the test passes
fine, and doesn't give an access violation.
While creating the new AssertEquals method, I purposefully created a
failure with then gives the access violation, instead to the
comparison message I expec
Oh, I forgot to mention. If the ObjectStates match, the test passes
fine, and doesn't give an access violation.
While creating the new AssertEquals method, I purposefully created a
failure with then gives the access violation, instead to the
comparison message I expected:
"Failing on 1: Expecte
