A look back at the best from this week in the past.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-03-31]
A look back at the best from a year ago.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-01-13]
A look back at the best from a year ago
Software development / Test Automation / Testing
Posted on:
John Henry, Manual Tester
There’s a piece of North American folklore about John Henry, who was a manual laborer during the expansion of the railroads in our country. His job was being replaced by steam-driven heavy equipment, as the railroad industry applied technology to become more efficient. The same dynamics are happening today with manual testers. We need to make sure that manual testers avoid John Henry’s fate – read on to see why.
Software development / Test Automation / Testing
Posted on:
Test Smarter, Not Harder – A Detailed Article
A detailed (15-page) article by Scott Sehlhorst showing how to incorporate test automation for complex software has been published at developer.*. This article shows the math, benefits, and weaknesses of traditional approaches to automating functional tests. The article also proposes improvements to the process, rethinking the problem to provide innovative solutions. This post discusses the background for the article and provides an overview, as well as links to related content.
Agile / Foundation series / Process Improvement / Software development / Test Automation / Testing
Posted on:
Foundation Series: Functional Testing of Software
Functional Testing, also referred to as System Testing of software is the practice of testing the completed software to confirm that it meets the requirements defined for the software. A functional test is typically a test of user interactions, but can also involve communication with external systems. We contrast functional testing with unit testing. We also show how functional testing provides different benefits than unit testing.
Communication / Consulting / Product Management / Requirements / Software development / Testing / Use Cases
Posted on:
Communicate Relevant Quality Metrics
Most teams think about testing in terms of code coverage – what % of the lines of code are covered? What matters to our stakeholders is how well the software works. More precisely, how well does the software let the users work? We should be targeting our quality message in terms of use cases, because that matches their perspective and context.
Process Improvement / Software development / Test Automation / Testing
Posted on:
Learn to Fly with Software Process Automation
We can reach the next step in our software process evolution by automating much of our process. Flying squirrels evolved a technique* to quickly move from one tree to another without all the tedious climbing and dangerous running. Software teams that automate their processes achieve similar benefits. Automation allows us to increase efficiency while improving quality. And we spend less time on tedious and mundane tasks.
Communication / Process Improvement / Requirements / Software development / Software requirements specification / Testing
Posted on:
Passing the Wrong Whitebox Tests
We’ve talked about the value of using whitebox testing in our Software testing series post on whitebox testing. What we haven’t explored is how to make sure we are creating the right tests. We have to validate our tests against the requirements. This post shows where the flaw is in the typical whitebox testing process, and how to fix it.
A reader emailed us with the comment, “It’s been my experience that developers can’t test their own code.” Their problem was that they were missing a link in the software development chain (missing a step in the process).