Hi Juan,
NCrunch has no deliberate constraints like this ... as far as I know, the code you've described should work correctly.
I am aware that having tests with the same namespace, class and method name can cause issues, as NCrunch uses these three pieces of information to uniquely identify them. However, in your case, the namespaces are different, so the tests should be shown and tracked separately from each other.
I've just tried a few tests myself, and I can't seem to reproduce this issue with a code sample. Is there any chance you could throw together a project that produces this problem and submit it through the
contact form? I wonder if there is something deeper here that is amiss.