Post on 10-May-2015
description
K3 Keynote
10/2/2013 4:30:00 PM
"Lightning Strikes the Keynotes"
Presented by:
Lee Copeland
Software Quality Engineering
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
Lee Copeland
Software Quality Engineering
With more than thirty years of experience as an information systems professional at commercial
and nonprofit organizations, Lee Copeland has held technical and managerial positions in
applications development, software testing, and software process improvement. Lee has
developed and taught numerous training courses on software development and testing issues
and is a well-known speaker with Software Quality Engineering. Lee presents at software
conferences in the United States and abroad.
9/23/2013
1
Lightning Strikes
The Keynotes
Moderated by
Lee Copeland lee@sqe.com
Featuring
Julie Gardiner and
Pablo Garcia Munos
Jon Bach Jennifer Bonine
Griffin Jones Clinton Sprauve Dawn Haynes
Hans Buwalda
Rob Sabourin Geoff Horne
James Bach
Melissa Tondi Bill Curtis Pradeep Soundararajan Matt Heusser
9/23/2013
2
James Bach
9/23/2013
3
Jon Bach
9/23/2013
4
Julie Gardiner and
Pablo Garcia Munos
9/23/2013
5
Jennifer Bonine
9/23/2013
6
Hans Buwalda
Misconceptions of
Test Automation (and keyword testing)
Hans Buwalda
9/23/2013
7
Comments:
" automation is easy, no need to think about it much "
I'm still waiting to see my first "easy" automation project
Development is hard, testing is harder, automated testing is the
hardest
If you can't do automation well, be ready to lose time and money
However, if you can do automated testing well... good for time-to-
market, good for quality-to-market, good for business bottom line
Timely automated functional testing is particularly also a holy grail
for agile projects ("same sprint")
Comments:
" test automation means automating manual tests "
A car is not the same as a carriage with an engine
Good automated testing is not the same as good automation of good
manual testing
Automating manual test designs tends to be cumbersome, uninspiring,
maintenance sensitive, and hard to scale
How you organize and design your tests is the main driver for automation
success
+ =
9/23/2013
8
Comments:
" keywords is a method "
Keywords are not much more than a format to write tests in, in itself
not much different from (good) coding of test cases
Some of the worst tests I have seen were keyword tests
I do believe however that keywords are just about the only way to go
for big and complex projects (in addition to exploratory testing). They
just need a method
In my approach organization of tests into "test modules" plays a
central role
Test Module Plan
Tests
Objectives
Test Module 1
Tests
Test Module 2
Tests
Test Module N
Actions
. . .
AUTOMATION
Objectives Objectives
user password
log in jdoe StarEast
first last brand model
rent car John Renter Ford Escape
rent car John Renter Chevrolet Volt
last total
check bill Renter 140.42
Example of a method with keywords:
"Action Based Testing"
interaction test business test
window control value
enter log in user name jdoe
enter log in password StarEast
window control property expected
check prop log in ok button enabled true
9/23/2013
9
Comments:
" to do automated testing you need to be a good programmer "
A C++ programmer who is working on an airplane control system is not
therefore automatically a good airline pilot
A good programmer is not automatically a good tester, or vice versa I therefore don't believe we should replace all testers with "developers in test"
Successful automation depends much more on test design and test
organization than on technical skills
Even automation itself is a craft that is different from regular programming
Comments:
" you need an ROI analysis to determine which tests to automate "
One of the most commonly found statements on test automation
In my view, in a good automated testing effort, the automation itself is
a secondary practical matter
I therefore prefer to see an ROI on the tests themselves, rather than
on their automation
$ $
$ $ $
$ $
$
$ $
$
$ $ $
$ $
$
$
(ROI stands for "Return On Investment")
9/23/2013
10
Comments:
" automated tests are dumb "
It is the responsibility of the testers to ensure tests are not dumb lame tests are not likely to find interesting bugs
automation is not an excuse
True is that automated tests are often mechanical and boring, but they
don't have to be
Try to be focused, smart, and mean to the system under test . . .
To help: distinguish between an analytical activity ("what to test") and
creative activity ("how to test")
" homework "
Are these misconceptions ???
" if there are automation problems, debug your automated tests"
"test automation is the same as programming"
"the most important activity in an automation effort is selecting a tool"
"automation is most suitable for regression testing"
"test automation is a technical challenge"
"if you use keywords your test automation will be successful"
"to have more automation, you just need more people"
9/23/2013
11
Rob Sabourin
9/23/2013
12
Dawn Haynes
9/23/2013
13
Geoff Horne
9/23/2013
14
Griffin Jones
WREST Workshop on Regulated Software Testing
Software subject to review by an internal or external regulatory body
9/23/2013
15
More Information
Next WREST: October 4th 2013
Contact:
John McConda, Griffin Jones
Website: wrestworkshop.com
A Simple Tool …
9/23/2013
16
Blank Poster Paper
What is Meaningful To You
Information Radiator
Easily Accessible (Digitize it)
Listen for the Music it is Singing to You
Quotes or Memory Triggers
9/23/2013
17
9/23/2013
18
9/23/2013
19
9/23/2013
20
Clinton Sprauve
9/23/2013
21
Melissa Tondi
9/23/2013
22
Bill Curtis
9/23/2013
23
Pradeep Soundararajan
9/23/2013
24
Matt Heusser
9/23/2013
25
Our Thanks To
Julie Gardiner and
Pablo Garcia Munos
Jon Bach Jennifer Bonine
Griffin Jones Clinton Sprauve Dawn Haynes
Hans Buwalda
Rob Sabourin Geoff Horne
James Bach
Melissa Tondi Bill Curtis Pradeep Soundararajan Matt Heusser