What’s your definition of 100% coverage? Do you even believe it’s possible to achieve in a testing environment? It all depends on your definition of coverage.
Michael Bolton notes that skilled testers will approach any “100%” claim about coverage with critical thinking, as any such claim should prompt a number of questions designed to gain deeper insight into the details of the supposed coverage. Oftentimes, team members will use the phrase “100% coverage,” but unless more information is provided, they could be ignoring several important aspects of said coverage.
Bolton goes on to provide a helpful way of thinking about the issue. View it and the rest of his article here.
To develop a comprehensive performance testing strategy, teams may write a “performance equation” which includes a number of factors that must be checked and validated. However, author Albert Gareev argues that individual pieces do not always equal the whole picture—he warns against overlooking performance-affecting components.
As testing is much more about the discovery of systems’ behaviors than the verification of a few samples of expected behavior, Gareev uses this article to present and evaluate each part of the performance equation: the test environment, workload scripts simulating user activity, application code, and performance characteristics (e.g. response time, throughput, etc.).
In last week’s roundup, we featured a Software Testing Help (STH) article that discussed whether or not it was worth getting a QA Software Testing certification. This week, they’ve followed up with a post explaining the different types of certification available at every level of tester’s career.
If you’re interested in becoming certified, use this list as a guide. For each certification option, it includes important details like eligibility requirements, fees, how to apply, links to register, tips on how to prepare, and the exam format you’ll be faced with. To identify the best certification options based on your experience level, check out STH’s compressive list here.
Due to the widespread adoption of agile development methods, testing teams have had to adapt. Author Sanjay Zalavadia asserts that many of these teams are realizing that they need new skill sets and a better understanding of what exactly “agile” means for their jobs and the projects they undertake.
In this TechWell article, Zalavadia explores the skill sets and information that teams need to have before an agile project can be undertaken. Broken down into what you need to ask, understand, and do to successfully practice agile testing, this post is a must-read for any organization considering the shift to agile.