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 9252223
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T10:53:28+00:00 2026-06-18T10:53:28+00:00

I have NUnit running into VS2012 with the NUnit Test Adapter and I can

  • 0

I have NUnit running into VS2012 with the NUnit Test Adapter and I can do Run All tests fine, but if I want to Debug All Tests every time I hit an Assert it throws an exception. How do I make it not throw exceptions for Asserts? Am I doing something horribly wrong?

  • 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-06-18T10:53:29+00:00Added an answer on June 18, 2026 at 10:53 am

    When the debugger is attached, failed asserts throw exceptions. This is intended behaviour. No need to be alarmed.

    You can stop Visual Studio from stopping at certain exceptions, by going into Debug -> Exceptions… and unchecking all or some items in the appropriate group, from the column “Thrown” in the “Break when an exception is:” box.

    The Exceptions dialog box

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

Sidebar

Related Questions

I have a Set of TestFixtures running fine. I added a new Test into
I have a Nunit test which adds message into MSMQ. In the teardown of
I have a few NUnit tests that run Selenium. There are some prerequisite to
I have an MSBuild script that uses NUnit to run tests in two assemblies.
I have a problem: if i run this test in NUnit ,it works Board
I have a nunit class library containing test cases. I want to programmatically get
We have a CruiseControl server running various AntUnit, MbUnit and NUnit tests via Ant.
I'm running some NHibernate tests with NUnit and the NUnit test agent is crashing.
We have tests using WatiN that we want to run on our CruiseControl.NET server.
I'm running the NUnit tests and everything is fine as long as the required

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.