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

  • Home
  • SEARCH
  • 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 91227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T22:59:49+00:00 2026-05-10T22:59:49+00:00

I have methods with more than one parameter that are guarded against bad input

  • 0

I have methods with more than one parameter that are guarded against bad input by throwing ArgumentNullExceptions and ArgumentExceptions whenever any parameter is null.

So there are two obvious ways to test this:

  • One test per Parameter using the [ExpectedException] attribute
  • One test for all parameters using multiple try{} catch blocks

The try catch thing would look like that:

try  {     controller.Foo(null, new SecondParameter());     Assert.Fail('ArgumentNullException wasn't thrown'); } catch (ArgumentNullException) {} 

With one little problem. If the test passes, Assert.Fail never gets called and will therefore be highlighted as not covered test code (by NCover).

I know this isn’t actually a problem, since it’s the business code I want 100% coverage of, not the test code. Still I am curious if there is a way to compress multiple Exception throwing calls into one Testcase without having dead LoCs?

  • 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. 2026-05-10T22:59:49+00:00Added an answer on May 10, 2026 at 10:59 pm

    From release notes of NUnit 2.4.7 NUnit now includes the RowTest extension, written by Andreas Schlapsi, in it’s extension assemblies. This extension allows you to write test methods that take arguments and to provide multiple sets of argument values using the RowAttribute. To use RowTest, your test must reference the nunit.framework.extensions assembly.

    It adds to NUnit the RowTest feature from MbUnit.

    You can than write something like:

    [RowTest] [Row(1, 2, 3)] [Row(3, 4, 8, TestName='Special case')] [Row(10, 10, 0, TestName='ExceptionTest1'     , ExpectedException=typeof(ArgumentException)     , ExceptionMessage='x and y may not be equal.')] [Row(1, 1, 0, TestName='ExceptionTest2'     , ExpectedException=typeof(ArgumentException)     , ExceptionMessage='x and y may not be equal.')] public void AddTest(int x, int y, int expectedSum) {   int sum = Sum(x, y);   Assert.AreEqual(expectedSum, sum); } 

    http://www.andreas-schlapsi.com/2008/03/31/nunit-247-includes-rowtest-extension/ The code is from source code for Nunit RowTestExtension at Google code

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

Sidebar

Related Questions

I have a method that is receiving more than one parameter. The method signature
Is it good practice to have more than one try{} catch{} statement per method?
I need to change an interface that is used by more than one app.
I have 2 exporter methods (planning to have more) that essentially take my sprite
I know for more than one result, you don't have much choice for using
More often than I'd have hoped I seem to come across method/property definitions in
I have methods in all of my models that look like this: def formatted_start_date
In C# I have methods that use [WebMethod(EnableSession = true)] I consume them in
Some existing web services I consume have methods that look something like this: List<Employee>
I have opended a question about repeated parameter-checks in public methods. The result there

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.