This document discusses how testing has changed with the adoption of agile and DevOps practices like CI/CD. While these changes aim to improve quality and speed, they can also introduce new problems for testers with increased time pressures and tooling issues. The document suggests ways testers can adapt, such as integrating more with development practices, using more advanced test automation techniques and tools, and focusing testing on risk areas identified through data and production usage insights. It also discusses how artificial intelligence techniques like robotic process automation could be applied to testing activities.

1. Advanced Testing
Techniques
How Can We Save Testing?

2. Hello!
I am James Farrier
Find me at investingintesting.com
Thanks to SlidesCarnival for helping with these slides!

3. SDLC Journey - How Has Testing Changed

4. Waterfall - Was It Really That Bad?

5. Agile - The First Big Change

6. CI/CD - Are We There Yet?

7. Devops/Automation

8. Ask The Audience
Quiz Time Part 1

9. Is your
organization
“Agile”?

10. Have they joined
the Devops
movement?

11. Do you find
yourself dreaming
about continuous
improvement?

12. Is CI/CD your
favourite thing to
talk about?

13. Despite all this
awesomeness, do
you still have
problems with
your testing?

14. What’s Changed? Are Testers Better Off?

15. “It is not the strongest of the
species that survive, nor the
most intelligent, but the one
most responsive to change
– Charles Darwin

16. “Intelligence is the ability to
adapt to change.
– Stephen Hawking

17. Time
Scope
Resources
Quality

18. Time

19. How Do We Fit Everything In?

21. Automation Saves The Day?!

22. “The most powerful tool we have
as developers is automation.
– Scott Hanselman

23. “With automation at this level, the
new “ops guy” won’t care if he’s
responsible for a dozen systems
or 10,000.
- Mike Loukides,
What is DevOps?

24. Ask The Audience
Quiz Time Part 2

25. Do you find
yourself waiting
forever for your
tests to finish
executing?

26. Do you have tests
failing for the
strangest of
reasons?

27. Are important
issues difficult to
find due to flaky
tests clouding
your view?

28. Are you always
searching for the
right piece of
information?

29. Is your life spent
organizing your
tests and sorting
the mess caused
by flaky tests?

30. Are you tired of
being unable to
determine why a
test failed?

31. Does the same
defect ruin
multiple tests?

32. Are some tests
always red,
leaving you with
“Boy who cried
wolf syndrome”?

33. Is your email filled
with “spam”?

34. Do you prioritize
your tests and test
runs?

35. Are you always
searching for
environments?

36. Are you happy
with the tooling
available to QA?

37. Quotes from
industry experts...
And some not so expert

38. “If you automate a mess, you get
an automated mess.
– Rod Michael

39. “Failure in your automation can indicate
more than just failure in your tests, but
possibly issues within your organization.
Automation can't be used as a bandaid
to fix organizational problems.
– James Farrier (me)

40. MORE PROBLEMS
Are Our Tools Working For Us?

41. Test Tools - Common Issues
● Testing is an after thought.
● Built by devs primarily for devs or
project/product managers.
● Built in the 90’s.
● Poor integration with other tools.

42. Test Tools - Examples
Test Runner - Jenkins - Built for devs by devs.
Defect Management - Jira - Most over
complicated basic website ever built.
Agile Project Management - Version One -
Testing is an after thought. No bugs, wtf...
Test Case Management - Excel - Built before
exploratory testing, poor automation integration.

43. Is Testing Dead? Can’t The Devs Just Do It?

44. Quality Is More Important Than Ever

45. More Competition and Technically Minded Users

46. “The price of light is less than the
cost of darkness.
-Arthur C. Nielsen, Market
Researcher & Founder of
ACNielsen

47. “War is ninety percent
information.
-Napoleon Bonaparte, French
Military and Political Leader

48. How Can Testers Join The Revolution?

49. Agile Process
Integrate ourselves more into the Agile
Process.
● Understand Unit Tests.
● Code Reviews.
● Start Pair Programming.
Push for new tools which work for
testers. Push back on poor quality.

50. Advanced Tools
Test Runner - Cluster Runner by Box.
Reporting - Allure, Extent.
Reporting/Monitoring - Splunk,
Prometheus, ELK.
Parallelized Execution - SauceLabs,
Selenium Grid Extras.

51. Device Management - BBC Hive

52. Device Management - Open STF

53. Allure

54. ELK

55. Advanced Techniques
Static Analysis - Indicating Possible
Problem Areas.
Mutation Testing - Better Code
Coverage Stats.
Pact Testing - More Advanced
Integration Testing.

56. Targeted Testing
Data:
● Static Analysis.
● Logs.
● Performance.
● Previous Defects.
Production Usage - Changes In User Behaviour,
Usage Anomalies (i.e. Same Action).
Screenshot Changes - Applitools.

57. Robots - Using Artificial Intelligence For Testing

58. Creating a Bot - Interactions

59. Creating a Bot - Data

60. Creating a Bot - Rewards

61. Creating a Bot - Bots From Bots

62. Using Your Bot

63. Monkeys can write
Shakespeare?
Can bots write our
applications?

64. Thanks!
Any questions/positive feedback?
jamesfarrier@gmail.com
Any other feedback?
jamesfarrier+spam@gmail.com
For the latest in testing innovation
http://investingintesting.com