Databases
StackOverflow2013
Postsdbo
POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
    primarykey
    data
    text
    <p>Let's pretend I have 3 classes that each have exactly one responsibly (and method). Let's also pretend that these classes have interfaces to facilitate dependency injection. Class A calls the interface for class B and class B calls the interface for class C. If class C throws a NotAPrimeNumberException (if say, the int parameter isn't a prime number), I would expect to have a unit test that makes sure that C throws an NotAPrimeNumberException if the passed in parameter isn't a prime number. So far so good.</p> <p>I'm currently under the belief that the unit tests provide all of the documentation I need to understand the behavior of the method being tested. So the aforementioned unit test would be something like MakeSureNotAPrimeNumberExceptionIsThrownIfNumberisNotPrimeTest().</p> <p>Class B knows that class C can throw a NotAPrimeNumberException. If I want to let the NotAPrimeNumberException bubble up out of class B should I write a unit test for class B to somehow check that a NotAPrimeNumberException is thrown in some circumstances? What about Class A? If A also lets the NotAPrimeNumberException bubble up, should it also have a unit test for this?</p> <p>My concern is that if I DON'T write a unit test in Class B then the consumers for class B won't be aware that class B can throw this type of exception. However, if I DO write the unit test then it is a little silly that I have to force the call to class B to throw a NotAPrimeNumberException only to NOT handle the exception in class B. If I don't write a unit test, what is the appropriate way, if any, to document in the API that this exception can occur?</p> <p>The bonus question is how do you facilitate this in NUnit with Rhino-mocks? This is of course dependent upon the first two questions.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjakejgordon
    1. USjakejgordon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
      1. USScott
      1. VTFavorite
    2. VO
      singulars
      1. POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTest should pass when the expected behavior happens. Even if that behavior is throwing an exception.
      singulars
      1. POUnit Testing Multiple Levels Of Exceptions -- Where To Stop?
      1. USStefan H
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload