expected-exception

How do you do the equivalent of: [Test, ExpectedException( typeof(ArgumentOutOfRangeException) )] void Test_Something_That_Throws_Exception() { throw gcnew ArgumentOutOfRangeException("Some more detail"); } ...in C++ (the example there is C#)? As far as I can see, there's no typeof() function for the C++ implementation of NUnit. To avoid anyone else hunting around for ages trying to find it, here's the solution: [Test, ExpectedException( ArgumentOutOfRangeException::typeid )] void Test_Something_That_Throws_Exception() { throw gcnew ArgumentOutOfRangeException("Some more detail"); } Simply use

I need to write a unit test for the next function and I saw I can use [ExpectedException] this is the function to be tested. public static T FailIfEnumIsNotDefined<T>(this T enumValue, string message = null) where T:struct { var enumType = typeof (T); if (!enumType.IsEnum) { throw new ArgumentOutOfRangeException(string.Format("Type {0} is not an Enum, therefore it cannot be checked if it is Defined not have defined.", enumType.FullName)); } else if (!Enum.IsDefined(enumType, enumValue)) { throw new ArgumentOutOfRangeException(string.Format("{1} Value {0} is not does not have defined value in

This is weird, but all of a sudden the ExpectedExceptionAttribute quit working for me the other day. Not sure what's gone wrong. I'm running VS 2010 and VS 2005 side-by-side. It's not working in VS 2010. This test should pass, however it is failing: [TestMethod] [ExpectedException(typeof(ArgumentNullException))] public void Test_Exception() { throw new ArgumentNullException("test"); } Any ideas? This really sux. Steve Py Not to resurrect a dead thread, but I came across this when this all the sudden happened to me, in case it can help others. I did finally track down what the problem was,

I am trying to work with the ExpectedException attribute in a C# UnitTest , but I am having issues getting it to work with my particular Exception . Here's what I got: NOTE: I wrapped asterisks around the line that is giving me the trouble. [ExpectedException(typeof(Exception))] public void TestSetCellContentsTwo() { // Create a new Spreadsheet instance for this test: SpreadSheet = new Spreadsheet(); // If name is null then an InvalidNameException should be thrown. Assert that the correct // exception was thrown. ReturnVal = SpreadSheet.SetCellContents(null, "String Text"); **Assert.IsTrue

I'm using SpecFlow, and I'd like to write a scenario such as the following: Scenario: Pressing add with an empty stack throws an exception Given I have entered nothing into the calculator When I press add Then it should throw an exception It's calculator.Add() that's going to throw an exception, so how do I handle this in the method marked [Then] ? Great question. I am neither a bdd or specflow expert, however, my first bit of advice would be to take a step back and assess your scenario. Do you really want to use the terms "throw" and "exception" in this spec? Keep in mind the idea with bdd is

This is my test so far: @Test(expected = FileNotFoundException.class) public void testExpectedException() { UserDataObject u = new UserDataObject("rob123", "Smith", "Robert", "Danny", 1); FlatFileStorage ffstorage = new FlatFileStorage(); ffstorage.verifyUser(u, "dsfsdfsfdsdf.txt"); However, the test seems to fail! Even though when I run it, the error message actually gets printed out from the method on the console too, like this dsfsdfsfdsdf.txt (The system cannot find the file specified) Am I missing something really obvious here? EDIT** Here is the method I'm actually testing public void