While it is a nice feature, the string argument to an MSpec [Subject] attribute (the Concernparameter) isn't necessarily supposed to be the name of a method of the subject. I believe it is intended more to be descriptive text, as in (for example):
TestFX appears to cause this parameter to be treated as a method name and it get's highlighted in red and flagged (by ReSharper, I think) as an error when it doesn't correspond to a method name:
I'm not sure what mechanism causes this behaviour, but it doesn't happen with MSpec. I don't know if this is right or wrong, but I think it is at least worth opening a discussion as to whether this is desirable as it seems to suggest a different intent than that used in MSpec.
While it is a nice feature, the string argument to an MSpec [Subject] attribute (the
Concern
parameter) isn't necessarily supposed to be the name of a method of the subject. I believe it is intended more to be descriptive text, as in (for example):TestFX appears to cause this parameter to be treated as a method name and it get's highlighted in red and flagged (by ReSharper, I think) as an error when it doesn't correspond to a method name:
I'm not sure what mechanism causes this behaviour, but it doesn't happen with MSpec. I don't know if this is right or wrong, but I think it is at least worth opening a discussion as to whether this is desirable as it seems to suggest a different intent than that used in MSpec.