Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Best practices for unit testing are that you should only write for each test a single assertion. In this article intends, Jonathan Allen tries to demonstrate that unit tests with multiple assertions are both necessary and beneficial.
In this blog post, Mark Prichard presents a solution on how to use Jenkins to give a “QA dashboard” view of a native Android application build. His goals were to show metrics for the results of unit test and code coverage in an Android build context on the Jenkins continuous integration system.
In this blog post, Jonathan Kohl discusses the similarities between software testing and game playing. He defines a game as a “situation involving cooperation and conflict with different different actors with different motivations and goals”. He sees software testing as an individual pursuit within a larger software development game and with two styles: scripted testing and exploratory testing..
In this article, Andrew Hunter shares his opinion that unit tests and test driven development (TDD) now dominate the types of test that are used in software development. This situation has limited the attention available for other software testing types, such as the integration tests. Thus he asks the question: “Are unit tests overused?“
In this article, Cem Kaner explores the technical concept of software testing coverage and the legal concept of software negligence. The article discusses the idea of complete coverage and the trade-off that software developers have to make when testing software. The main idea is that complete coverage is a misleading concept. “This “completeness” is measured only relative to a specific population of possible test cases”. You might achieve line coverage, but to achieve path coverage, you must test every path through the program and this is an impossible task. The goal of the software tester is to prioritize among tests in a careful way. This means to select the test strategy that could be rationally considered as the most likely to find the most bugs or the most serious bugs. This article has an appendix that lists 101 coverage measures.
This article from David Sale provides a short introduction to Behavior-Driven Development in Python. The article presents the principles of Behavior Driven Development and present the syntax of the Gherkin language that can be used with the freshen Python package, a clone of the famous Cucumber BDD framework written for Ruby. Freshen is an open source acceptance testing framework for Python that uses (mostly) the same syntax as Cucumber. A small step by step example is provided on how to use freshen and alternative tools are proposed.
If you are a good software tester, but if you can’t communicate well what you find, you provide little value and are not very useful to your project team. This article gives you some hints specific to mobile applications testing on how to become a great bug reporter. Your teammates will love you for this and you will prove your value as a skilled team member.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates