Unit Testing has moved from fringe to mainstream, which is great. Unfortunately, developers are creating mountains of unmaintainable tests as a side effect. Jay Fields has been fighting the maintenance battle pretty aggressively for years, and this talk captures what he believes is the most effective way to test.
PHP is not the best language to catch errors in code, like mistyped names of variables. This is what static code analysis tools (named linters or lints) can do: find bugs in code before it ever get executed. Linters don’t replace unit tests, but generally they are faster and cheaper to set up. I’ll talk about my XRef lint project (http://xref-lint.net/) as well as other helpful open source alternatives: phplint (http://www.icosaedro.it/phplint/), arcanist (http://phabricator.org/) and scrutinizer (https://scrutinizer-ci.com/).
Mockito is a popular open source mocking framework for Java code. In this article, Marcin Grzejszczak explains how you can use Mockito by adding it to different paths. You will also learn how to implement new tests by using Mockito hints and warnings.
QualiTest has recently produced a report and an infographic about the typology and sources of the most common bugs found in web sites. The company has used for this the bug summaries from hundreds of web site testing projects performed recently.
Exploratory testing is a concept of software testing where the tester combines application learning, test design and test execution in the same activity. This approach can showcase the results that a skilled tester can provide with manual tests. In this article, Kimberly A. Stockett provides three key approaches about how to change the attitudes of your software development team to adopt exploratory testing.
Tests should save our money and time. How is it that they often become the stumbling block and slow down the work? They fail every time you try to do some refactoring and are difficult to maintain ultimately increasing the cost of software maintenance.
Skilled software testing has not fit well into the culture of Agile development. Agile was not created by testers, or with testers, or with deep testing in mind. As a result, people who study and practice the testing discipline have done so largely outside of Agile culture. To help fix this, the “Agile Testing Quadrants” should help you explain a better way for testing and development to coexist.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates