The software testing industry's buzzwords can be hard to decipher at times, especially when trying to explain these buzzwords to fellow co-workers within your organization who don't really have a clue what you're talking about. Buzzwords are unavoidable, however, there needs to be a clear understanding of what a buzzword is and the testing buzzwords you should know.
2. @neotys
Is the website going
to be ready for
Black Friday?
Well, we’re in the middle
of crowdsourcing tests for
likely user scenarios.
Sanity checks have gone
well but we haven’t run a
full automated regression
yet. Plus, Jimmy is going
through some exploratory
work now.
@neotys
16. @neotys
BUT WHAT DOES
ALL *THIS* MEAN?
Testing as a Service
Smoke Testing
Crowdsourced Testing
Continuous Integration
Test Automation
Sanity Check
Exploratory Testing
17. @neotys
WE’RE ABOUT TO BREAK
IT DOWN FOR YOU
Testing as a Service
Smoke Testing
Crowdsourced Testing
Continuous Integration
Test Automation
Exploratory Testing
Sanity Check
21. @neotys
1. CROWDSOURCED TESTING
It’s not terribly predictable, and doesn’t
scale very far, but for the right cases it can
be extremely effective.
It’s also a great way to get a community
aware of what you are building.
@neotys
23. @neotys
2. TESTING AS A SERVICE
Outsourced testing services, where a 3rd
party takes your script and executes a bunch
of testing on your behalf.
@neotys
24. @neotys
2. TESTING AS A SERVICE
Suitable for:
• Unique environments
• Short-term bursts of specialized activity
• 3rd-party verification (security, audits)
@neotys
25. @neotys
2. TESTING AS A SERVICE
TaaS providers may operate with heavy
automation in a well-equipped lab, or they
may be crowdtesting experts.
@neotys
27. @neotys
3. SMOKE TESTING
Back in the day… this was pretty literal.
Today, smoke testing is a cursory, preliminary
system check. A gatekeeper.
@neotys
28. @neotys
3. SMOKE TESTING
Smoke testing checks the basics:
• Does it start?
• Does it run?
• Can a user log in?
• Can a user execute a transaction?
• Can the administrator view the dashboard?
@neotys
29. @neotys
3. SMOKE TESTING
Because when you kick off a long series
of tests and go home for the night, you
don’t want the system to crash 5
minutes after you leave.
@neotys
32. @neotys
4. SANITY CHECK
Smoke tests
• Ensure the software is stable
• Test core functionality
• Are automated and repeated
Sanity checks
• Validate new features or fixed bugs
• Check that changes are actually there
• Are ad-hoc and unscripted
@neotys
36. @neotys
5. REGRESSION TESTING
Did we create more
bugs than we fixed?
Does everything that
worked yesterday still
work today?
@neotys
37. @neotys
“
5. REGRESSION TESTING
When I think about regression
testing, I think about any testing
that involves the reuse of tests
(manual or automated) or test
ideas (regression charters for
example — a regression test
does not necessarily need to be
the exact same test) to manage
the risks of change. This could
include testing for bug fixes,
testing to make sure a bug fix
didn’t break something else.
Mike Kelly
http://michaeldkelly.com
@neotys
39. @neotys
Give a man a fish,
feed him for a day.
Teach a man to fish,
feed him for a lifetime.
6. TEST AUTOMATION
@neotys
40. @neotys
QA used to be all about manual testing &
finding bugs.
Today, modern QA organizations are coders,
who make computers do this work for them.
Test automation improves scale, quality,
efficiency – you name it!
6. TEST AUTOMATION
@neotys
41. @neotys
Many people think test automation is limited
to functional testing. Not true.
More and more, test automation applies to
many other areas like load & performance
testing – automatically validating that
software behaves well under load and stress.
6. TEST AUTOMATION
@neotys
44. @neotys
7. CONTINUOUS INTEGRATION
CI relies heavily on automated testing. Every
time code is checked in, a large test suite is
run to make sure nothing is broken.
CI ensures a consistent level of high quality
software, avoiding large disruptions that
break builds for days at a time.
@neotys
45. @neotys
7. CONTINUOUS INTEGRATION
CI is a change to the organization that
requires a high degree of:
– Collaboration
– Communication
– Transparency
– Automation
– Teamwork
That’s why strong teams love it!
@neotys
48. @neotys
8. EXPLORATORY TESTING
Many people think it’s ad-hoc
testing, but actually it’s an approach
that is concisely described as
simultaneous learning.
While methodically test a product,
the tester learns how it behaves, and
identifies its strengths and
weaknesses.
@neotys
49. @neotys
“
8. EXPLORATORY TESTING
A style of software testing that
emphasizes the personal
freedom and responsibility of
the individual tester to
continually optimize the
quality of his or her work by
treating test-related learning,
test design, test execution,
and test result interpretation
as mutually supportive
activities that run parallel
throughout the project.
Cem Kaner
@neotys
50. @neotys
THAT WASN’T SO BAD.
WAS IT?
Testing as a Service
Smoke Testing
Crowdsourced Testing
Continuous Integration
Test Automation
Sanity Check
Exploratory Testing