View
206
Download
0
Category
Preview:
DESCRIPTION
The testing tools marketplace is flooded with products that address very specific parts of the quality management lifestyle. Many of these tools have been around, in one form or another, for the best part of 20 years. As a result, they are inflexible and, quite frankly, do not apply to today’s way of working. Others are more recent innovations, typically open-source and, on the surface, shiny and new. However, once we get past the shiny wrapper, they tend emulate their significantly older relatives. As such, the currently available support infrastructure tends not to deliver benefits, only overhead. In this presentation from our Webinar session you will explore how the current tool sets limit our agility in an ever-changing environment. Tim Bower, Solutions Architect, introduced some alternative approaches that could allow flexibility in our way of working and, most importantly, our way of thinking. Discover what you should be demanding from the tools industry and why... http://www.origsoft.com/solutions/software-test-automation/
Citation preview
Shaping the Future of
Testing Tools: Escaping the 1990s!
Tim Bower
Senior Solutions Consultant
Original Software
(Assisted by Dilbert)
Introductions
Original Software
SQA & AQM - 14 years
500 customers
Home of
» Code free automation
» Dynamic Manual testing
» Top to bottom
Tim Bower (me)
Very Old
Developer, Tester, BA
Been in IT since it was called DP
History of Testing
Until 1956 – Debugging oriented
1957–1978 – Demonstration
oriented
1979 – Glenford J. Meyers
introduced the separation between
debugging and testing
1979-1982 – Destruction oriented
1983-1987 – Evaluation oriented
1988-2000 – Prevention oriented
History of Testing Tools
Y2K - very significant event
Test Automation gained the
‘spotlight’ in the 1990s as a
result of the impending event
Mercury Interactive’s WinRunner
– Possibly the most famous
First ‘tool’ appeared 29 years
ago
Tool writers have been busy…
Market According to Gartner
Management Driven Testing
Management View of ALM
Design Build Test Deploy
Design Build Test Deploy
What it feels like……
Build
Test
Deploy Design Test
Hands up all QA/Testing engineers and managers
Keep your hands up if you report into the development function
Now hands up if reporting into the business
And finally hands up if into an independent Head of QA
Quality in the organisation
Management view….
I want these systems
delivered sooner and
working perfectly.
Why can’t I have that?
A fair question?
Testing Bottleneck.
Needs automation.
That did not help.
Need experts. A TCOE!
That did not help.
Offshore it.
That did not help.
The problem moved
Agile!
Testing Industry Evolution
B
T
D
Time passes…..
Agile means…
Alignment of Teams
What is the point of tools?
Better
Faster
Cheaper
Productivity
Quality
Silver bullet?
Science project or get in & go?
Scripting code
Code
Line
Coded testing
Test automation
Easy to learn
Easy & quick to build
Easy to update
Extendable
Full function
Robust to change
Reliable
Widely applicable in the team Dev, QA, UAT, BAU…
Modern Automation Requirements
Afterthought Regression
Sp 1 Sp 2 Sp 3 Sp 4 Build regression
Not a separate sprint.
Sp 1 Sp 2 Sp 3 Sp 4
Regn Regn Regn
Not overflowing the sprint.
Regression Deliverable
Des
Code
FT
RT
Sprint 1 Sprint 2 Sprint 3
ReF
Des
Code
FT
RT
ReF
Des
Code
FT
RT
ReF
Design
Code, TDD
Refactor
Functional Test
Regression Test
Regression in each sprint
Easy, Flexible
Avoid toxic debt – bugs and scripts
Automation is the use of machines, control
systems and information technologies to
optimize productivity in the production of goods
and delivery of services.
The correct incentive for applying automation is
to increase productivity, and/or quality beyond
that possible with current human labor levels so
as to realize economies of scale, and/or realize
predictable quality levels.
Agile Automation
Automated Manual Testing
Evolve into automation
Not specialist skills
Quick to build
Disposable if necessary
Can be built upon
Helps the team
and delivers when
Done is Done!
Agile Automation
AQM Challenges
Collaboration
Metrics
Traceability
Presentation of Metrics and Results
Frequency
Recency
Baselines and Versions
Workflow
Data
Knowledgebase
Defining the Solution
Agility
Flexibility
Velocity
Applicability
Integration
Cost of ownership
AQM breadth and depth
Measure
Predict
Respond
Automation heavily reliant on code will slow you
down.
Employ technology to help all parties,
technology they can use.
Encourage collaboration and unite the team
Quality is a team responsibility.
Get immediate, relevant data to manage by.
Conclusion
Questions?
Tim Bower – tbower@origsoft.com
www.origsoft.com
Please fill out our feedback form as you leave
Recommended