Hi!
I got a problem with OleDBException with Nunit 2.4.1 and 2.4.3. When I execute the method Open it call the methode OpenConnectionToExcelFile.
In the method open we catch the OleDBException and with Nunit 2.4.1 and more the information is wrong in the catch. In attachment you have the difference between the same code executed with Nunit 2.4.1(2.4.3) and TestDriven + the code too.
The result for TestDriven is the same as Nunit 2.2
We need to have the NativeError which is not available under the latest version
Everyting was ok with Nunit 2.2
P.S we still using Framework 1.1, we tought it was the problem but with driven it's working fine
Thanks!
Code + stuff
Logged In: YES
user_id=586918
Originator: NO
Can you provide a test case? Preferably one that works in NUnit 2.2 but
not in 2.4? Since all contributors don't use the same software, it's
helpful not to depend on other products.
Charlie
PS: Please use text rather than Microsoft word for an attachment - or
just paste the sample code in your post here. Thanks.
Test Case Code
Logged In: YES
user_id=1901327
Originator: YES
File Added: ProblemOleDBException.txt
Logged In: YES
user_id=1901327
Originator: YES
I just add the code for the Test probleme
Thanks!
Logged In: YES
user_id=586918
Originator: NO
SF rejected my email reply to your note, so I'm posting it here...
No change yet - it will be reported on the bug when it is. I'm just getting into the final push for release 2.4.4, so I'll see if there is something I can do with it quickly. Your test case will help a lot there.
Charlie
Logged In: YES
user_id=586918
Originator: NO
This is not going into the 2.4.4 release. It's a bit complicated and doesn't yet have a clear test case.
Can you tell me the last NUnit release on which you have seen this work correctly? I saw the same behavior on 2.2.10 and 2.4.2.
Is there a simple test we can run, which tests that NUnit is handling the exception correctly? This would be a lot easier than using the debugger.
Charlie
Logged In: YES
user_id=1901327
Originator: YES
The last version we use on wich the test past was 2.2.0. If you use Test Driven with the same code the test past