Comment 3 for bug 1065254

Hi, I looked into this. The problem is that the class name that we give to VS in this case is xxx.MyTestClass(42). I don't think it's related to generic fixtures but I assume we have a similar problem there.

The fix is very simple, it's the same removal of trailing parenthesis wrapping the arguments values that we do for methods already, but I noticed that the tests that we have in place right now cannot cover these cases, apparently because we follow two different approaches to create the tests in the real code and in the test code (which imply a different naming).
IOW, the class in the example inside our own tests will get the name xxx.MyTestClass rather than xxx.MyTestClass(42), which is what happens in the real use case. We will probably need to change our testing approach to cover these cases.