Software Testing

An engineering approach to testing

In my previous post, I argued that a system can be declared successfully tested when: all the regulations, requirements, specifications, or imposed conditions have been tested the product meets all the clearly stated needs of all the stakeholders. In some applications, especially those critical for safety and security, that’s not enough: it’s necessary to know also how much code has been tested, if there’s unreachable code around, how many conditions have been evaluated, etc. This Read more…

Discovering Bugs, or Ensuring Success? Both!

An interesting article written by¬†Yegor Bugayenko, founder and CEO of Zerocracy, published in the last number of the Communications of the ACM, enters the neverending debate on how much testing is enough to ensure that a product can be safely commercialized. There has to be a certain point where testers stop looking for bugs. […] Finding bugs motivates testers, and they’ll keep looking for them. At some point, you have to launch the product. But Read more…