Pushing the Boundaries of Test Automation
This blog post presents some results of an exploration of software testing tools to discover various types of potential user interface issues even for complex applications.
This blog post presents some results of an exploration of software testing tools to discover various types of potential user interface issues even for complex applications.
In this blog post, Alberto Savoia discusses the CRAP (Change Risk Anti-Patterns) code metric. The CRAP metric combines cyclomatic complexity and code coverage by automated tests to help identify code that might be particularly difficult to understand, test or maintain.
This article provides 3 tips to create readable unit tests.
This post tries to summarize the high level basics of writing testable code.
A test is not a unit test if: * It talks to the database * It communicates across the network * It touches the file system * It can’t run at the same time as any of your other unit tests * You have to do special things to your environment (such as editing config files) to run it.
In this blog post, Alister Scott explains why it might be better to write acceptance tests in a different language than your code.
This video show how and why we should all be doing test reviews on our peer’s code. It talks about basic rules to look for in test code and reviews some of the tests of public open source projects.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates