Software Testing Tutorials and Videos
The test documentation set includes all the documents we create to describe the testing effort. This includes test descriptions, testing project schedules, bug reports, summary reports, etc. Historically, there has been a substantial push in our industry for large sets of standardized documents, coming out of the history of our …
There have been some studies both about the concept of Testability and how to implement it, many of which use test hooks. In spite of its obvious benefits, we still find low adoption of testability concepts. Why is there not more emphasis on core testability principles? In this analysis we …
All tests automation systems have certain common tasks. Different tools tend to focus on some tasks and put less emphasis on other tasks. While examining 11 home-grown test automation tools at F5, we found certain patterns. There were six different tasks that all tools addressed to varying degrees. We found …
This presentation by Elfriede Dustin and Marcus Borch at the Third Annual Google Test Automation Conference (GTAC) discusses our various efforts to streamline automated software testing implementations. By “automating the automation” via use of existing open source tools, component “reuse” and by automating as much as feasible related to automated …
The ultimate goals of any software-testing effort is to make the software more robust and reliable, thereby reducing support costs and increasing customer satisfaction. Recent trends to use unit testing and other techniques in the software build process help reach those goals. However with the move towards systems of interacting …
Whenever unit-tests are written, chances are good that the code is not isolated. Many tests run against a given class/interface/function. The design didn’t consider isolating the dependencies of this function, which makes tests slower, larger, less focused, and likely depending on external dependencies (e.g. database access) which decreases the reliability. …
