REVIEW: How many developers does it take to test a product?

 REVIEW: 

How many developers does it take to test a product?

by Wayne Rash

OVERVIEW: A collection of feedback from specific and named software organizations on how they form their development teams.

Summary Quotes:

"While in most cases, for every two to five developers, one tester would be fine..."

"many variables come into play, ranging from the availability of automation tools in testing to the income reliability of the project, to how much of the testing can be automated"

Software Criticality factor - "mission critical applications, including automotive, heavy truck, and mining equipment product development. A single failure could lead to death or disaster."

Further thoughts from the reviewer:  We need a way to rate the efficiency and skills of test team.  AKA some warm bodies can reduce the efficiency of a test team.  We need consistency on how we generate test cases and determine coverage.  We need software test optimization!

Comments

Post a Comment

Popular posts from this blog

Don't Let This Be YOU: Mazda bricks Radios with Software Defect

Image
 ARS Technica article on Mazda radio defect by  JONATHAN M. GITLIN  -  2/9/2022 SummARY: A critical real-time defect in Mazda radios was triggered by a Seattle radio station.  If you were unfortunate enough to have this  2014 to 2017  Mazda radio and live in the Seattle area listening to  94.9 FM , the radio was no longer usable.  Files with no extension were (like .jpg) were the use case that sent the radio into constant reboot condition rendering it useless.  Read the full article at link above.  Yes, I was slow to find this gem.  Please share if you find more like it!
Read more

F35 System Testing

Image
Many calendar years of development and testing have gone into one of the most complex vehicle systems ever -  the F-35. This article details how performance and  End User / Operational Testing of F-35  is being performed.
Read more