The many types of asserts and their meaning, and dealing with assert bugs

Posted by: Rico Marianis Performance Tidbits, on 10 Oct 2015 | View original | Bookmarked: 0 time(s)

A good way to get a quick rise out of me is to tell me how you’re going to just delete some noisy assert in your code, or worse still, that some assert is “ignorable” – in fact I think the ignore button on the assert dialog is a crime against humanity.   I think the only buttons that should be on an assert dialog are debug and exit.  I’m actually surprised how much disagreement I find when discussing how to handle bugs that report assertion failures. ...

Category: Security | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 266 | Hits: 7

Similar Posts

  • Using Assert.AreSame more
  • MoQ now uses xUnit for its unit tests more
  • What data type should I use? more
  • Productive Unit Testing with Specialized Assertion Classes in MbUnit more
  • My Unit Testing Idea : Facilitating Multiple Assertions more
  • assert_required Plugin 0.1.2 more
  • JSUnit more
  • Test-driving Windows shell scripts with Windows Scripting Host more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD