In this blog post, Rob van Steenbergen add his humorous input to the current debate about the death of software testing. He mentions a lot of reasons why we should stop testing like: * a user will follow the manual strictly * a user will do no strange things with the software * a user will not make mistakes using the software Find many other reasons of this type in his blog.
The Unit Testing and Mocking Tools Directory presents a list of unit testing and mocking tools, both open source and commercial, for the main programming languages (Java, .NET, ruby, etc). It contains also a list of resources associated to this topic. Visit http://www.unittestingtools.com/
Every month, 50% of the Google code base changes. This is a lot of code and a lot of people. In order to ensure that its code base stays healthy, Google uses a bug prediction algorithm. This blog post discusses how Google develop this machine-learning and statistical analysis tools that tries to guess whether a piece of code is potentially buggy or not, usually within some confidence range. Bug prediction is not an objective measure by any means, but it is used to place a warning in our code review system on specific files. Whenever a reviewer logs in to review that code, the warning will appear, which hopefully will encourage them to spend some more time reviewing the code or hand off the review to someone more experienced if need be.
Web Consistency Testing is a new form of automated Web testing that answers the simple question “does this page look the way it should?”. Historically, the way a page looks has been relegated to the status of “design artifact” and as such, been treated as something that must be tested with human eyes.
SOA Web services are now supported by most of major software development companies and industry. To be reliable, these ones require to be developed with respect to a complete software development life cycle and, in particular, they need to be tested. Test purpose-based methods are black box testing techniques which take advantage of reducing the time required for test derivation in comparison with exhaustive methods.
This video provides a retrospective of what went right and, more importantly, what went wrong for the software testing activity during a transition to agile.. If agile is in your future, come discover what you’re in for, traps to avoid, and how to be successful. If you’re not ready for agile, you’ll learn some new approaches that can be applied to traditional processes.
One of the most common mistakes that teams made was treating specifications or related automation code as less important than production code. Examples of this are giving the automation tasks to less-capable developers and testers and not maintaining the automation layer with the same kind of effort applied to production code. Reference: “Specification by Example – How successful teams deliver the right software”, Gojko Adzic, Manning, 249 pages, IBSN 978-1617290084
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates