Of Faults and Errors: Who’s to blame?
Is there a difference between a “fault” and an “error” within a computer program? A number of people commented on my previous article suggesting this
Is there a difference between a “fault” and an “error” within a computer program? A number of people commented on my previous article suggesting this
The abort function is a remnant of old programming practices, and it pains me to see it in modern software. While it’s great that a
Asking questions about performance online universally invites scorn and accusation. A large number of programmers apparently feel that the efficiency of code is nowadays insignificant.
New languages try to improve the lives of programmers by simplifying some aspect of programming. Many make bold claims about eliminating certain types of errors,
We all know that operations in a computer happen one after the other. Having multiple CPUs and instruction reordering tends to obfuscate the issue. Technically
Is overloading a bad thing? Despite a wide variety of new languages supporting some form of it I continue to find articles that say overloading
One of the most common testing tools is equivalence classes. Most testers generally understand what they are and how to use them. They allow us to do full coverage of an application without needing to test every possible permutation of input. Yet, despite their popularity I find that the two most important, the two most vital classes, get overlooked. Here I’ll cover these two classes and their implications on testing.
Despite a huge push for more testing of applications, online or off, there is actually not a lot of standardized systems for doing it. This is not to say there aren’t a lot of standard techniques, there simply lacks unifying by-the-book approaches which yield solid results. A lack of standards should however be no reason not to test your web application. Yet without clear guidance most providers kind of just try things thereby wasting a lot of effort and still ending up with a poor quality product. Here is a general overview of the five basic approaches to testing.