Documente Academic
Documente Profesional
Documente Cultură
Future Solutions
June 24, 2008
Science Fiction – Fiction today, Reality tomorrow
Arthur C. Clark
Geosynchronous satellites
(1945) – Actual satellites
(1963)
Cloning - Dolly
2
What About These?
3
Assumptions
4
Problems in Testing?
5
Challenges in Testing
6
What does testing mean for different stakeholders?
Let us face it
Nobody wants testing…
If I assume testing is necessary I am likely to try to improve how to do
testing
If I believe testing is unnecessary expenditure I am likely to find ways
to minimize or eliminate testing
Mindset Matters
7
TESTING WORLD’S BIGGEST PROBLEM
8
HITE
9
How much time do I need to test it?
10
Bug – The Only Perfect Being
11
Whole Is More Than The Sum Of Parts
12
Whole Is More Than The Sum Of Parts
13
Integrated Environment
Design – Mapped
Requirements to Requirement
Visual
Prioritized
Self-checking
Testable
Constrained
14
Regression Test Selection Tool
15
Tool-Chain
Code based
models: UML Design based
Code models: UML
and future
and future
16
User Messages and API based test cases
Where is this
message called?
How?
Code and
Has it been
Repository of
called?
“user”
Has this log been
messages
generated?
Log messages
generated
17
Coverage & Data – Integral Part of Tool-Chain
External Standards
Interface Conformance Customer
Internet care –
coverage
security database,
advisories emails,
Code blogs
Security Requirement
check Coverage
Test
Code
Coverage
Data from Coverage
Defect
application
monitoring
database, data-
in mining for bug-
Non-
production taxonomy
functional
Coverage
18
New format for writing test cases: visual format
19
Ability to replay code
Crash
20
Far Future – Where Testing?
• Tool driven
• Integral part of development
• Better ways to tie all development artifacts together
• Integration with various sources of information
• Better analysis and action
21
Q&A