Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
The testing strategy to adopt when you you run your code inside a Java EE container is the topic discussed in this blog post by Antonio Goncalves. To solve this issue, he presents a detailed step by step process to unit test an EJB with Mockito and how to do integration test with and without Arquillian with code samples. His conclusion is that since Java EE 6 it is now easy to use container and services in an embedded mode. Unit testing is good to test business code or code in isolation (mocking external components) but you have to remember that you should also use integration testing to test code interacting with external components or services.
eXtreme programming is an Agile software development methodologies. It involves extremely short incremental release cycles, early and frequent testing, heavy use of design refactoring, and pair programming. This article proposes a process model called “ordered incremental testing” where guidance on test order is provided. Testing is conducted iteratively with very short iteration cycles as a single class is developed. Although early and frequent testing is very important, there is little guidance about specifics of the testing process.
Js-test-driver is an open source JavaScript unit tests runner written in Java. The project was started at Google and is under active development. This article provides a step by step process on how to JSTestDriver to write tests for Javascript. This article starts with an overview of the tool architecture before explaining its configuration, how to run js-test-driver from the command line and how to run it from Eclipse. The main part shows how to write tests and presents the most important features of js-test-drivers. Debugging of tests in Firefox and Chrome is also discussed.
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.
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.
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.
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
