« Service Orientation, Law of Demeter | Main | Clemens on Transactional Queues »

2004.12.10

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83451806669e200d83456faaa69e2

Listed below are links to weblogs that reference Testing VB6 with NUnit:

Comments

Fiach Reid
Any ideas on how to apply this technique to VB6 .EXE's rather than DLL's?
Todd Girvin
No, man. Sorry I can't help you there. I'm not doing VB6 dev anymore so I don't even have an environment to experiment. Testing is one motivation for separating out "application services", or services provided by an application into a DLL and making your EXE just the presentation layer with your forms and such. Of course, the other reason is just good layering practice to separate concerns between presentation, app service, domain logic, and persistence.
alex
Just use simplyvbunit to use VB6 unit testing (exes as well as dlls) and avoid paying fees for software. http://simplyvbunit.sourceforge.net/
jimbo
hi there. is there a way that you can test the DLL's private methods? thanks.
Todd Girvin
I don't think you can access the private methods of a DLL because they aren't listed as entry points. That's an issue in .NET, too, as we sometimes have to make methods public just to get at them for testing. That being said, I bet someone has devised a crafty way around it using attribution and lookup tables or something. If you could collect the function pointer in one place, a test tool to jump right to the functions being tested. But accessing private members in Windows DLLs would normally be a potential security hole.

The comments to this entry are closed.

November 2008

Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            
Blog powered by Typepad

We Like