We have migrated VB6 code to C# in .net

Question

The code was migrated using a third party tool. what ever the tool couldnt do, was done by the .net developers, so that all compile issues were fixed. My question is, for such migration activities, do we not bother running unit tests for the functions.

Secondly, Could anyone suggest if we should use some tool in VSTS 10 to create a UML model of this code to minimize risks of issues that the client might find. How cumbersome is it.

Are there any other suggestions for how quality migrated code can be delivered, in light of the fact that the functionality of the original VB6 application is unknown to us.

Answer 1

for such migration activities, do we not bother running unit tests for the functions.

I wouldn't trust freshly translated code (mechanical or otherwise) at all. Absolutely it needs testing.

the functionality of the original VB6 application is unknown to us.

That will make regression testing quite... challenging. If you don't know how it is meant to behave, how do you know when you've finished it?

Of course, you could decide not to unit test the translated code, then you won't know how the new code works either - not sure that "unknown = unknown" counts as a "pass", though.