This blog post is about my notes on slide set for BBST Foundations lecture 6: Measurement

Reading Time: 1 minute

This blog post is about my notes on slide set for BBST Foundations lecture 6: Measurement.
In reading Michael Bolton (2007),What Counts?, Michael explains trap in test counting measurement. If you want to take into discussion about measurement in software testing with Michael, you need to read Michael Bolton (2009), “Meaningful Metrics” as a requirement.
Reading Doug Hoffman (2000), “The Darker Side of 
Software Metrics”, explains some popular testing metrics traps. My favourite are side effects of metrics (Wally will buy himself a minivan by writting a lot of bugs).
Cem Kaner and Walter P. Bond (2004), in “Software engineering metrics: What do they measure and how do we know?” answers the question: How do you know that you
are measuring what you think you are measuring?
Erik Simmons (2000), “When Will We Be Done Testing? Software Defect Arrival Modelling with the Weibull Distribution”, gives example of applying Weibull distribution on three different projects.
As a software tester, you have to measure software value to relevant stakeholders.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Notes on slide set for BBST Foundations lecture 5: The impossibility of complete testing.

Reading Time: 1 minute

This blog post is about my notes on slide set for BBST Foundations lecture 5: The impossibility of complete testing.
First read is from Doug Hoffman (2003). “Exhausting your 
test options”. Interesting example how to test sqrt function.
Second reading is from Cem Kaner (1997), The Impossibility of complete testing. We are not quality assurance because we are not authorised to make all moves that will assure quality. We are doing “Good enough testing”.
Third reading is “Factors that influence 
test estimation” by Rex Black. Lists all factors that must be considered when putting out testing effort estimation. “Blog: When do we stop a test?” by Michael Bolton is self descriptive. Cem Kaner (1996), “Negotiating testing  resources: A collaborative approach.” Is about test plan estimations. Mike Kelly, “Estimating testing using 
spreadsheets” gives step by step example how to use spread sheet for testing estimation for Windows Calculator.
Combinatorial mathematics is very important testing tool. It is used to determine testing coverage.
What is complete testing?
1. Run all distinct tests. Test are distinct if they expose bugs that other test will miss.
2. We know that there are no bugs in software.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Notes on slide set for BBST Foundations lecture 4: Programming fundamentals and coverage.

Reading Time: 2 minutes

This blog post is about my notes on slide set for BBST Foundations lecture 4: Programming fundamentals and coverage.
First read: “SOFTWARE NEGLIGENCE AND TESTING COVERAGE” by Cem Kaner. Gives list of 101 coverage measures. Yes, you read it right. There are 101 different coverage measures!
Second reading is “How to misuse code coverage by Brian Marick”. Tool for code coverage is not a hammer, but it can help a lot. Summary: “Developers care more about whether their code does what was intended; product testers care more about whether what was intended is right. Because product testers are looking for requirements-level or specification-level omissions, coverage provides fewer and weaker clues than it does to developers, who are looking for design-level and code-level omissions.”
Third reading is “Got you covered by Michael Bolton”. What is complete testing? All possible test having been perfectly performed. There are known unknowns, and there are unknown unknowns.
Fourth reading is “What every computer scientist should know about floating point arithmetic” by David Goldberg. I skimmed over it. It is detailed paper about floating number format in computers. If your stakeholder business depends in great amount about floating point operations, you will read this paper in detail.
Following reading has interesting title: “An interview with the old man of floating point”.
Sixth reading is “Experience with the cost of different coverage goals for testing”.Gives for which coverage types is reasonable to set 100% coverage using unit testing.
I skimmed that reading. I also skimmed reading book: Charles Petzold (1993), Code: The Hidden Language 
of Computer Hardware and Software. The book explains codes using examples form everyday life. From best friends to modern computers.
The we have: overflow concept, data representation systems (binary, decimal), float, data structures, coverage.
Recommended reading book: “Introduction to software testing”
Interesting interview: http://www.exampler.com/testing-com/writings/iview1.htm. I heard for the first time concept of testing requirements that I like very much. It is similar to my notion of common sense requirements.
“””You use coverage analysis to assure quality of your set of tests, not the quality of the actual product.”””

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather