software testing’s future—according to lee copeland
TRANSCRIPT
1
Lee CopelandSoftware Quality Engineering
@grandpacopeland
Creating a Better Testing Future
The World Is Changing andTesting Must Change With It
22
Topics
• Our World is Changing
• The Curse of Past Successes
• Lee’s Don’ts and Do’s for Future Success
• In the past, organizations controlled external communication, both content and channels
• Today, with the rise of Social Media …
66
Communication is Changing
77
Communication is Changing
• Organizational structure controlled tester communication, both content and channels
• Today, social media can immediately connect testers world-wide
99
Development Process Is Changing
• COBOL• CICS• VSAM
• C#• Java• HTML 4/5• JavaScript• XML• SQL• noSQL
Then
Now
1212
Topics
• Our World is Changing
• The Curse of Past Successes
• Lee’s Don’ts and Do’s for Future Success
1414
The Curse of Past Successes
• Processes that made us successful in the past may prevent us frombeing successful in the future
2020
Topics
• Our World is Changing
• The Curse of Past Successes
• Lee’s Don’ts and Do’s for Future Success
2323
Organization
• DON’T
– Maintain teams of “developers” and “testers”, throwing products over the wall
– This was supposed to foster “independence.” Instead, it created “us vs. them” and “huh?”
Development Test
2424
Organization
• DON’T
– Establish Testing Centers of Excellence
– “It’s where the disengaged gather to not produce”
– David Hussman
2727
Test Process
• DON’T
– Cling to a Waterfall style when your organization is moving toward Agile
3030
Test Process
• When we already believe something to be true, we verify our belief by checking. Checking is a process of confirmation, verification, and validation
• Checking is a highly automatable process
3131
Test Process
• Testing is something that we do with the motivation of finding new information
• It is a process of exploration, discovery, investigation, and learning
• Testing is not automatable. It’s using our brain in real time, and it’s really fun
3333
Test Process
• DO
– Focus on “What Value Does Testing Add?”
rather than “What Processes Does Testing Execute?”
3939
Planning
• DON’T
– Adopt rigid, overly detailed plans
– Restrict testing to explicit requirements
– Remember: “No battle plan survives contact with the enemy”
– Helmuth von Moltke
4040
Planning
• DO
– Create plans that
Tell a story
Present essential data
Inspire and communicate
Describe a reasoned plan of action
4747
Automation
• DO
– Use Exploratory Testing
“Simultaneous learning, test design, and test execution.”
– James Bach
4848
Automation
• DO
– and Session-based Exploratory Test Management
Perform Exploratory Testing in Sessions:
Charter
Timebox
Reviewable result
DebriefingJon Bach
5050
Focus on Prevention Over Finding
• DO
– Remember, while finding defects is important
– We should be focused on defect prevention activities
5252
Thanks for Attending
Shamelesscommercial
message