53
1 Lee Copeland Software Quality Engineering [email protected] @grandpacopeland Creating a Better Testing Future The World Is Changing and Testing Must Change With It

Software Testing’s Future—According to Lee Copeland

Embed Size (px)

Citation preview

1

Lee CopelandSoftware Quality Engineering

[email protected]

@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

33

Technology Is Changing

Then

Now

44

Customers Are Changing

Less loyal to brands

Expect more capability

Less tolerant of low quality

55

Business Is Changing

• 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

88

Development Process Is Changing

Then

Now

99

Development Process Is Changing

• COBOL• CICS• VSAM

• C#• Java• HTML 4/5• JavaScript• XML• SQL• noSQL

Then

Now

1010

Testing Must Match Today’s Technology

IEEE 829 Testing

Standard

19831983 1987

1111

Testing Must Match Development

1212

Topics

• Our World is Changing

• The Curse of Past Successes

• Lee’s Don’ts and Do’s for Future Success

1313

The Curse of Past Successes

1414

The Curse of Past Successes

• Processes that made us successful in the past may prevent us frombeing successful in the future

1515

The Curse of Past Successes

Camera Film

1616

The Curse of Past Successes

Video Rental Stores

1717

The Curse of Past Successes

Newspapers

1818

The Curse of Past Successes

Brick and Mortar Stores

1919

The Curse of Past Successes

Getting Bills in the Mail

2020

Topics

• Our World is Changing

• The Curse of Past Successes

• Lee’s Don’ts and Do’s for Future Success

2121

The Don’ts and Do’s

Focus

2222

The Don’ts and Do’s

Organization

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

2525

Organization

• DO

– Integrate developers and testers together on the same team

2626

The Don’ts and Do’s

Test Process

2727

Test Process

• DON’T

– Cling to a Waterfall style when your organization is moving toward Agile

2828

Test Process

• DON’T

– Try to test EVERYTHING

2929

Test Process

• DON’T

– Confuse Checking with Testing

Michael Bolton

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

3232

Test Process

• DO

– Adopt a Customer-focused approach to testing

3333

Test Process

• DO

– Focus on “What Value Does Testing Add?”

rather than “What Processes Does Testing Execute?”

3434

The Don’ts and Do’s

Technology

3535

Technology

• DON’T

– Use Stone Age techniques, tools, and technologies

3636

Technology

• DO

– Embrace new technologies

3737

Technology

• DO

– Consider open source test tools

3838

The Don’ts and Do’s

Planning

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

4141

The Don’ts and Do’s

Automation

4242

Automation

• DON’T

– Rely on Capture/Replay

4343

Automation

• DON’T

– Try to automate every test

4444

Automation

• DON’T

– Try to replace humans in testing

4545

Automation

• DO

– Use Test-driven Development

4646

Automation

• DO

– Use Acceptance Test-driven Development

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

4949

The Don’ts and Do’s

Focus

5050

Focus on Prevention Over Finding

• DO

– Remember, while finding defects is important

– We should be focused on defect prevention activities

5151

The Don’ts and Do’s

Focus

5353

My Thanks To

• Dorothy Graham

• David Hussman

• Jonathan Kohl

• Alon Linetzki

• Dan North

• Martin Pol

• Rob Sabourin

• Alan Shalloway

• Adrian Zwingli

For their ideas, review, and comments