Agile Developers Go Testing Part II. Darcy Casselman @ flying_squirrel Alexei Zheglov @az1. November 2010. What are we talking about today?. A lot of things… They may seem disconnected, but they all: improve software quality involve testing done by developers
Darcy Casselman @flying_squirrel
Alexei Zheglov @az1
"...in 2000, during the dot-com bubble, ... software quality for North American teams... ranged from 6 defects per function point to less than 3 per 100 function point, a range of 200 to 1. The midpoint is approximately 1 defect per 0.6 to 1.0 function points. This implies that it is common for teams to spend more than 90 percent of their effort fixing defects.”
“The midpoint is approximately 1 defect per 0.6 to 1.0 function points. This implies that it is common for teams to spend more than 90 percent of their effort fixing defects.”
How does he know what they are spending their time on?
Capacity Allocation To Fixing Defects
Defect Injection Rate
Source: Karl Scotland
and certainly not like Team B
Source: GojkoAdzic. Bridging the Communication Gap, pp. 78-79
The system offers free delivery to Ontario customers when they place their first order and their order contains at least three books
Break the dependencies
System Under Test
Source http://www.osherove.com/blog/2010/9/10/2010-poll-which-isolation-framework-do-you-use-in-net.htmlSeptember 2010
Design for Testability:
Moq, RhinoMocks, etc.
Mock Anything, e.g.
Typemock Isolator, JustMock
Rely on Profiler API
Can intercept anything and run something else instead
Can fake statics, sealed classes, etc.
Don’t force design for testability
(and this is a simple example)
(different box color = different life span)