You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very cool that Assert is no longer a static class, which allows us to add extension methods and access the singleton "Assert" instance using Assert.That. However, is there a reason why the Assert constructor is public? I'd expect private, or at least Internal.
Steps to reproduce
var a = new Assert();
Expected behavior
I'd expect this not to work.
Actual behavior
Works. But is there a reason why you would ever need/want to do this?
Environment
Latest MSTestV2 on VS2015.
The text was updated successfully, but these errors were encountered:
Description
It's very cool that Assert is no longer a static class, which allows us to add extension methods and access the singleton "Assert" instance using Assert.That. However, is there a reason why the Assert constructor is public? I'd expect private, or at least Internal.
Steps to reproduce
var a = new Assert();
Expected behavior
I'd expect this not to work.
Actual behavior
Works. But is there a reason why you would ever need/want to do this?
Environment
Latest MSTestV2 on VS2015.
The text was updated successfully, but these errors were encountered: