Can I Integrate Nunit With Visual Basic 6.0 ?

Question

0.00/5 (No votes)

See more:

Hi All,

I was wondering whether I could integrate Nunit with Visual basic 6.0 since I am in need of a unit testing tool for my VB6.0 project.

I heard Nunit was great for .NET , can some one help me out here?

PS: I googled , couldn't find any relevant answers.

Thank you!

Posted 24-Sep-14 23:55pm

Shobin Parameswaran

Add a Solution

Comments

[no name] 25-Sep-14 6:15am

I doubt you will find anything. VB6 is dead and it's not a .NET language so a .NET unit testing framework would not do anything for you.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

PhilLenoir · Answer 1 · 2014-09-25T03:04:00

If the VB6 to be tested is a DLL then you can build a .NET wrapper to each DLL function by adding a COM reference in a .NET project to the DLL and run the tests against the wrapper layer. The wrapper layer should do no more than pass arguments/results in and out.

If the VB6 code is not a DLL, can you call/invoke the units to be tested in a test DLL?

Ultimately it might be more work than writing a test harness yourself and automating result reports if you need documentation.