The tester’s dilemma’sDebate
© 2013, René Tuinhout
2
Program
3
Introductions
• Roles in programming and testing → test manager / test advisor / practice lead / tutor
…René Tuinhout
4
5
Let’s start
6
History (1/6) – The people
9-9-1947
7
History (2/6) – The people
Bron: Wikipedia
Quality: the total of features and characteristics of a product or service that bear on its ability to satisfy stated or implied needs (ISO 8402)
Quality: The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]
Quality: is a relative concept, it is relative to a set ofrequirements (ISO 9000)
8
History (3/6) – The models
http://www.pg.com.ua/welcome_eng.htm
9
History (4/6) – The roles
• Pioneers
• Early professionals (using a framework)
• Professionals (using framework within profession)
10
History (5/6) – The tester´s spot
Acceptance Test
Component Integration Test
Component Test
System IntegrationTest
System Test
User needs,Requirements,
Business processes
SystemSpecification
Technical Design& Code
11
History (6/6) – The tester´s spot
• Change from “do it yourself” to hiring and outsourcing;
• From “Build from scratch” to “combining what´s there”;
• Model based development and -testing;
• Economic developments (crises)
• …
12
13
Now(1/6) – The people
…
14
Now(2/6) – The roles
• Tester• Test analyst• Test engineer• L&P tester• Performance Tester• Usability tester• Test coordinator• Test manager• Test change manager• Test continuity manager• Test advisor• Blended roles• …
15
Now(3/6) – The tester´s spot
Component Integration Test
Component Test
System IntegrationTest
System Test
User needs,Requirements,
Business processes
SystemSpecification
Technical Design& Code
Acceptance Test
16
Now(4/6) – And more
• Models for outsourcing;• SOA, development methods• Model based• DevOps teams• …
17
Now(5/6) – Questions and answers
What does the customer want?
Well tested products?A speedy time to market?Affordable testing?
De customer wants a good product.
Do you need testing for that?Basically, your customer doesn’t care:Even if you’d have to run a marathon for it…
18
Now(6/6) – Conclusion
Conclusion:
It’s about the product, not about the testing!
19
20
Debate – Some rules
• An thought will be presented
• If the location allows, form two groups (pro & con)
• Please raise your hand if you have an opinion regarding this thought
• The moderator selects the order in which opinions, arguments and counterarguments are expressed
• Please stand when expressing your opinion
• Please try to formulate concisely
• The time for discussion is limited,and will be moderated
21
Thought
“To be able to test properly, you sometimes have to
break the law”
22
Thought
“Test managers are obsolete”
23
Thought
“Stakeholders should be prevented from changing
requirements after acertain date”
24
Thought
“The test profession will go extinct within 10 years
from now”
25
Thought
“Agile development will replace waterfall
development”
26
Thought
“Test expertise can not be measured by standardised
certificates”
27
Thought
“Each and every test project is unique.
Therefore, every test project needs a new,
unique, way of working.”
28
Thought
“Not properly testing software after
development should be punishable by law”
29
Thought
“Every test can and should be automated.”
30
Thought
“Requirements cause much more bugs than code
does”
31
Thought
“Testing should be more about reviews and
inspections, and less about code execution”
32
Thought
“When using automatedtesting, 100% coverage
can be reached”
33
Thought
“Testing, in essence, is about ticking check boxes”
34
Thought
“It’s a great day in testing, the day that 0 defects are
found”
35
For slides and discussion topics
If you would like to receive the slides presented, please leave your name and e-mail address and I’ll send you a .pdf.
The tester’s dilemma’sDebate
© 2013, René Tuinhout
René [email protected]
nl.linkedin.com/in/renetuinhout