Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6219165
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T07:43:57+00:00 2026-05-24T07:43:57+00:00

Is there a way to write that I’m expecting a certain exception for certain

  • 0

Is there a way to write that I’m expecting a certain exception for certain inputs when I use the Factory attribute?
I know how to do it using the Row attribute but I need it for dynamically generated test inputs.

See test example bellow for a function that returns the inverse of the provided string:

[TestFixture]
public class MyTestFixture()
{
   private IEnumerable<object[]> TestData
   {
      get
      {
          yield return new object[] { "MyWord", "droWyM" };
          yield return new object[] { null, null }; // Expected argument exception
          yield return new object[] { "", "" };
          yield return new object[] { "123", "321" };
      }
   }

   [Test, Factory("TestData")]
   public void MyTestMethod(string input, string expectedResult)
   {
      // Test logic here...   
   }
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T07:43:57+00:00Added an answer on May 24, 2026 at 7:43 am

    I’m afraid that there is no built-in functionality to attach metadata (such as an expected exception) to a row of test parameters coming from a factory method.

    However, a simple solution is to pass the type of the expected exception as a test regular parameter (null if no exception is expected to be thrown) and to enclose the tested code in an Assert.Throws or Assert.DoesNotThrow method.

    [TestFixture]
    public class MyTestFixture()
    {
      private IEnumerable<object[]> TestData
      {
        get
        {
            yield return new object[] { "MyWord", "droWyM", null };
            yield return new object[] { null, null, typeof(ArgumentNullException) };
            yield return new object[] { "", "", null };
            yield return new object[] { "123", "321", null };
        }
      }
    
      [Test, Factory("TestData")]
      public void MyTestMethod(string input, string expectedResult, Type expectedException)
      {
        RunWithPossibleExpectedException(expectedException, () => 
        {
           // Test logic here... 
        });
      }
    
      private void RunWithPossibleExpectedException(Type expectedException, Action action)
      {
        if (expectedException == null)
          Assert.DoesNotThrow(action);
        else
          Assert.Throws(expectedException, action);
      }
    }
    

    By the way, it could be interesting to have an extra Assert.MayThrow assertion to get rid of the helper method. It could just accept null as the expected exception type. Maybe you could create a feature request here, or you may submit a patch.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there a way to write a custom validator that will perform different validations
Is there a way to write the following function so that my IDE doesn't
Is there a way to write a C code that allow us to determine
Is there any way to write a C program without a main function? If
Is there a way to apply several different csharp generic constraints to the same
I need to use LINQ to build a kind of weird query that uses
Problem I am trying to match the hash part of a URL using Javascript.
Is where a way to persist objects over re-execs of a running script? If
Suppose that I have the following record: type t = {a:int} In order to
Xcode 4 has a very nice built-in help/documentation that you can access e.g. by

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.