bbraithwaite / mstestextensions Goto Github PK

Nice useful codes. Thanks.

BTW, Is there any way for me to check whether any method does NOT throw exceptions?

I was looking around the 'net for a better way to deal with exceptions in MSTest and found the blog post on contentedcoder.com (and subsequently this project). So far it looks great, I've pulled it off NuGet and given it a quick try, and would like to use it for personal projects, but I can't find any licensing information.

So, is there a specific license this project is released under, and if there is, can that be reflected either by mentioning it in the AssemblyInfo files, or in a license file in the project root? Thanks in advance!

The new async/await syntax is a very prominent feature of .NET 4.5, and I have found myself needing to Assert that async operations throw the correct sorts of exceptions.

With the current MSTestExtensions I cannot do the following:

ExceptionAssert.Throws<ArgumentNullException>(async () => await SampleArgumentNullException());

If methods that accepted Func instead of Action were implemented, this would be possible

I am thinking this is likely my syntax error. How should I write correctly to assert that this will throw an exception?
Thank you for a great addition to our community!

            Assert.Throws(  ()=>
          using ( new Impersonator( "myUsername", "myDomainname", "myPassword" ) )
          {
              string a = 'a';
          }

p.s. I am getting the below, so probably I would prefer to test the string.

System.ComponentModel.Win32Exception: Logon failure: unknown user name or bad password

AnneTheAgile

Please sign (strong name) your assembly. Only strong named assembly are allowed as a dependency for other strong named projects.

Signing may also require a maintained version number. The current Nuget version seems to be 4.0.0 but the assembly version and file version are still 1.0.0.0. This could lead to unexpected bugs if someone puts them into the GAC.

Hi, just wondering why you uppercase the exception message / expected message for doing string comparisons, rather than using (e.g.) StringComparison.CurrentCultureIgnoreCase?

The advantage of using the case-insensitive comparer is that if the assertion fails, the exception message doesn't yell at you ;-)

MSTestExtensions doesn't seem to work when used in VS2010, apparently because it was compiled with .NET 4.5 as target framework. I have 4.5 installed, but VS2010 treats it as 4.0:

• When including the assembly reference, I'm getting a warning about "MSTestExtensions, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL" targeting ".NETFramework,Version=v4.5" while the project targets ".NETFramework,Version=v4.0". (It says 1.0.0.0 even though Nuget downloaded 4.0.0?)
• When actually trying to use it in code, I get an error about missing type or namespace "MSTestExtensions".

Trying to work through some tests using Assert.Throws<T>, some of the tests are getting difficult to write due to certain exception types inheriting others. My specific issues are arising with ArgumentNullException and ArgumentOutOfRangeException, as both have ArgumentException in their inheritance hierarchy. Due to that, when I test for an ArgumentException, the assert passes even though the exception was a subtype.

Would it be possible to add a check along the lines of Assert.IsFalse(typeof(ex).IsSubclassOf(typeof(T))); around here, either as the default behavior or as an option similar to ExceptionMessageCompareOptions?

Would be happy to make the change myself and open a pull request depending on your contributor requirements, will likely just change it in a fork otherwise.