There is a priority list of best to worst something like this: 1. Types 2. Compile time assertions 3. Unit tests 4. Fatal run time assertions 5. Non-fatal runtime assertions 6. Documentation
This is the order in which you are most likely to quickly find a problem. Obviously 1 and 2 don't apply to Javascript although static analysis could be the equivalent. Anthony On 21/11/14 05:51, David Rajchenbach-Teller wrote: > I wasn't aware that we could whitelist an individual NS_ASSERTION. How > do we do that? > > On 20/11/14 17:24, Boris Zbarsky wrote: >> This sounds lovely. >> >> Note that in C++ for some of our test suites we already have this with >> NS_ASSERTION and for all test suites we have it with MOZ_ASSERT. >> Assuming, of course, that the test suite is run in debug builds... >> >> -Boris >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
