Keynote at Sanae Beer.EX: The Automationist's Gambit

•

0 gostou•43 visualizações

The document discusses exploratory testing and test automation. It advocates that exploratory testing and test automation should be used together, not separately. You cannot automate testing well without exploring features, and you cannot explore efficiently without some automated tests. The document also provides examples of how exploratory testing and test automation can inform and enhance each other when used as complementary techniques.

Software

@maaretp http://maaretp.com
The Automationist’s
Gambit
by Maaret Pyhäjärvi

@maaretp http://maaretp.com
2020 - historical film – 1 season

@maaretp http://maaretp.com
Black cannot retain the
pawn without incurring
a disadvantage.
White appears to
sacrifice the c-pawn.

@maaretp http://maaretp.com
The Automationist’s
Gambit
* Opening by sacrificing
material to win in the end

@maaretp http://maaretp.com
Time used on warning about
test automation is away
from succeeding with it.
* opportunity cost

@maaretp http://maaretp.com
Exploratory Testing
TEST DESIGN
TEST
EXECUTION
LEARNING,
AGENCY
IMPACTFUL RESULTS
* power to decide with
knowledge and attitude that
goes with power

@maaretp http://maaretp.com
Exploratory Testing?
TEST DESIGN
TEST
EXECUTION
MANUAL AUTOMATED

@maaretp http://maaretp.com
Contemporary
Exploratory Testing
MANUAL AUTOMATED
LEARNING,
AGENCY
IMPACTFUL RESULTS

@maaretp http://maaretp.com
You can't automate well
without exploring. You can't
explore well without
automating.

@maaretp http://maaretp.com
Algorithm
Bug
Test Cases
Test data
Openings

@maaretp http://maaretp.com
Traditional Exploratory Testing Artifacts

@maaretp http://maaretp.com
Test Strategy for E-Primer

@maaretp http://maaretp.com
The Automationist’s
Gambit
Test Automation is Documentation!

@maaretp http://maaretp.com
Single line
àSee it fail
àFirst test
àSame test but variables
àSame test but parameterized
àFailing test with a bug
àSpec to tests
àGuess the values that are likely to fail
àMultiple browsers
à…
àRuns in CI
Throwaway
automation?

@maaretp http://maaretp.com
Bugs Found
- Some of specified examples not properly recognized
And Missed…
- Text box resize is broken (my bad)
- Browser crashes with 32k+1 chars with spaces (tool)
- n and – and … messes up word count
- More specified examples not properly recognized

@maaretp http://maaretp.com
Automation in
Frame of
Exploratory Testing

@maaretp http://maaretp.com
Attended
Unattended
Moving Focus
Learning
Learning
Learning
Learning

@maaretp http://maaretp.com
UNIT
SERVICE
UI
Exploratory
Sprinkle On Top
Exploratory Testing
Contemporary
Exploratory Testing
UNIT
SERVICE
UI
E
x
p
l
o
r
a
t
o
r
y

@maaretp http://maaretp.com
Can You?
Test Code Collaborate Ideate
Learn

@maaretp http://maaretp.com
Gambit is an opening with
an appearance of sacrifice.
What is your opening and
what is your end game?

@maaretp http://maaretp.com
2020 2016
MIATPP
Most Influential Agile Testing
Professional Person
#PayToSpeak #TechVoices
#EnsembleTesting #EnsembleProgramming #StrongStylePairing
#ExploratoryTesting #TestAutomation
#ModernAgile
#AwesomeTesters
Maaret Pyhäjärvi (from Finland)
Email: maaret@iki.fi
Twitter: @maaretp
Web: maaretp.com
Blog: visible-quality.blogspot.fi
(please connect with me through
Twitter or LinkedIn)

Mais conteúdo relacionado

Semelhante a Keynote at Sanae Beer.EX: The Automationist's Gambit

Delivering continuously - easier said than done. As I joined my team delivering Windows Desktop products two years ago with the aspiration of implementing continuous delivery, I was told it cannot be done. It started from the fact that making a single release was five-day effort, and continued with “no user would allow us to deliver frequently”. Two years later, making a release takes us two hours and the way we work together looks very different. With the principle of fixing maintenance issues in the latest release has resulted in improved flow forward and savings of effort in supporting small number of releases. This talk goes through our lessons learned on the journey of shortening release cycles to a continuous daily flow. We’ve experienced three essentially different sets of practices, with the core difference coming from release frequency. The good place is when we deliver continuously. The soulsucking place is when we deliver on two week cadence. And the insane asylum is when we deliver just once at the end of the project. Think of it like this: a pool is not just a bigger bathtub. The things you can do in a pool are different to those you can do in a bathtub. While both are containers of water, they serve different purposes. It is the same with release frequency. While it is all still releases, the continuous ones enable different practices. More details: https://confengine.com/agile-india-2019/proposal/7961/practices-change-moving-to-delivering-continuously Conference link: https://2019.agileindia.org

Practices Change - Moving to Delivering Continuously by Maaret Pyhajarvi at #...

Agile Software Community of India

Agile India: Practices Change - Moving to Delivering continuously

Maaret Pyhäjärvi

AGRS2019: Breaking illusions with Testing

Maaret Pyhäjärvi

SLASSCOM: Breaking illusions with Testing

Maaret Pyhäjärvi

DDD Europe: Breaking Illusions with Testing (keynote)

Maaret Pyhäjärvi

Programming Assignments in Tester Interviews

Maaret Pyhäjärvi

Mob testing

Maaret Pyhäjärvi

MoT Sarajevo: How to get better at Exploratory testing

Maaret Pyhäjärvi

DevoxxUK: Learning programming through osmosis

Maaret Pyhäjärvi

STARWest: Make Your Team Awesome, Yes You Can!

Maaret Pyhäjärvi

Testbash Australia: Next Level Teamwork - Pairing and Mobbing

Maaret Pyhäjärvi

AppiumLite Keynote: Many Hats to Make a Tester

Maaret Pyhäjärvi

Agile Serbia: Exploratory Testing Explained and Experienced

Maaret Pyhäjärvi

Semelhante a Keynote at Sanae Beer.EX: The Automationist's Gambit (13)

Practices Change - Moving to Delivering Continuously by Maaret Pyhajarvi at #...

Agile India: Practices Change - Moving to Delivering continuously

AGRS2019: Breaking illusions with Testing

SLASSCOM: Breaking illusions with Testing

DDD Europe: Breaking Illusions with Testing (keynote)

Programming Assignments in Tester Interviews

Mob testing

MoT Sarajevo: How to get better at Exploratory testing

DevoxxUK: Learning programming through osmosis

STARWest: Make Your Team Awesome, Yes You Can!

Testbash Australia: Next Level Teamwork - Pairing and Mobbing

AppiumLite Keynote: Many Hats to Make a Tester

Agile Serbia: Exploratory Testing Explained and Experienced

Mais de Maaret Pyhäjärvi

ATAGTR '20 Keynote: Building status

Maaret Pyhäjärvi

MoT Cork: Exploring Realities of Testing - From Theory to Practice

Maaret Pyhäjärvi

Testing Voices '21 keynote: Testing Becoming Harder To BeValuable

Maaret Pyhäjärvi

TestJSConf: Go Find What We May Have Missed

Maaret Pyhäjärvi

SauceCon: It's More Complicated than THAT

Maaret Pyhäjärvi

TSQA: Something In The Way We Test

Maaret Pyhäjärvi

ATAGTR: Targeting Errors Of Omission

Maaret Pyhäjärvi

Pivotal Moments, Pivotal Experiences

Maaret Pyhäjärvi

Testing Assembly: From Observations to Insights on Test Specialist Careers

Maaret Pyhäjärvi

Let's Do a Thing and Call it Foo

Maaret Pyhäjärvi

Selenium Conf: Patterns to Whole Team Test Automation Transformation

Maaret Pyhäjärvi

A new generation of testing is emerging, led by testers who believe test automation is an inseparable part of how we do exploratory testing. Yes, you read that right: exploratory testing with test automation, and on unit, api, ui and e2e levels all at our reach with team collaboration. We work on acceptance criteria and examples in our short increments, yet people are at their most creative on what could go wrong when they use the product or a piece of the product as their external imagination. When we’re creative, we need to do things we can’t do by hand, using programming to extend our reach. When we’re learning, we need to take notes now and to keep for later, again using programming to replenish information we deem worthwhile. We want to work on exploring a category of bugs before implementing, and a category of bugs before releasing, and a category of bugs after releasing. Last year I worked with a team that was transforming from a traditional manual test case + test automation -based approach to contemporary exploratory testing. This year I work with another team that takes this style of testing further than we’ve taken it before with whole-team testing. Let’s learn from a practitioner’s examples of ideas leading into this, changes enabling this, and results we are seeing with contemporary exploratory testing.

AxiomSummit 2022: A Practitioner's Guide to Contemporary Exploratory Testing

Maaret Pyhäjärvi

MoT Sfax: Good Exploratory Testing Tactics for Taking Over Testing

Maaret Pyhäjärvi

Geekle QA: Automationist's Gambit

Maaret Pyhäjärvi

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

Maaret Pyhäjärvi

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

Maaret Pyhäjärvi

Hands off Exploratory Testing - Managing Testing at Scale

Maaret Pyhäjärvi

Selenium Summit 21: Contemporary Exploratory Testing

Maaret Pyhäjärvi

Mimmit Koodaa - Testiautomaatio on testauksen dokumentointia

Maaret Pyhäjärvi

Testing United - Social Software Testing Approaches

Maaret Pyhäjärvi

Mais de Maaret Pyhäjärvi (20)

ATAGTR '20 Keynote: Building status

MoT Cork: Exploring Realities of Testing - From Theory to Practice

Testing Voices '21 keynote: Testing Becoming Harder To BeValuable

TestJSConf: Go Find What We May Have Missed

SauceCon: It's More Complicated than THAT

TSQA: Something In The Way We Test

ATAGTR: Targeting Errors Of Omission

Pivotal Moments, Pivotal Experiences

Testing Assembly: From Observations to Insights on Test Specialist Careers

Let's Do a Thing and Call it Foo

Selenium Conf: Patterns to Whole Team Test Automation Transformation

AxiomSummit 2022: A Practitioner's Guide to Contemporary Exploratory Testing

MoT Sfax: Good Exploratory Testing Tactics for Taking Over Testing

Geekle QA: Automationist's Gambit

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

Hands off Exploratory Testing - Managing Testing at Scale

Selenium Summit 21: Contemporary Exploratory Testing

Mimmit Koodaa - Testiautomaatio on testauksen dokumentointia

Testing United - Social Software Testing Approaches

Último

KLARNA - Language Models and Knowledge Graphs: A Systems Approach

Neo4j

Facemoji Keyboard released its 2023 State of Emoji report, outlining the most...

rajkumar669520

Breaking the Code : A Guide to WhatsApp Business API.pdf

Meon Technology

OpenChain @ LF Japan Executive Briefing - May 2024

Shane Coughlan

Scenarios are the central artifact of the Behaviour Driven Development (BDD) process. Although many teams use scenarios and tools like Cucumber or SpecFlow to automate them, in many cases their scenarios contain a lot of details, particularly test data, and therefore they become too complicated to support collaboration with the business. The "essential" principle of scenario writing (scenario formulation) states that only those details should be included in the scenario that are relevant for the outcome. This talk provides help for those who struggle implementing this principle or would be interested to learn how you can create brief and maintainable scenarios.

Tree in the Forest - Managing Details in BDD Scenarios (live2test 2024)

Gáspár Nagy

Advanced Flow Concepts Every Developer Should Know

Peter Caitens

Studiovity film pre-production and screenwriting software

info611746

Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.

TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR

Tier1 app

A Comprehensive Appium Guide for Hybrid App Automation Testing.pdf

kalichargn70th171

10 Essential Software Testing Tools You Need to Know About.pdf

kalichargn70th171

In his book, The Nature of the Physical World, Sir Arthur Eddington commented that “We have to appeal to the one outstanding law — the second law of thermodynamics — to put some sense into the world.” This sense-making goes beyond the physical world, too. Entropy is also essential in the fields of information and communication theory. During this lecture for the Princeton Plasma Physics Laboratory, lecturer Andrea Goulet discussed the application of entropy-related concepts in two communication systems: software and collaborative teams. She examined how concepts that help us understand systemic statistical disorder, such as ergodic systems, Lyapunov exponents, Kolmogorov-Sinai entropy, and Shannon-entropy can help us optimize for both software quality and innovation. She also provided several domain-specific models: Lehman’s Laws and Conway’s Law for software, as well as new models from her own research that relate to entropy and innovation. Entropy helps us understand the world and achieve great things. There is an underlying beauty in its principles that we can use to advance scientific discovery. When we understand the subtleties related to balancing surprise and structure, we increase our chances for effective collaboration and finding novel solutions to complex problems.

Entropy, Software Quality, and Innovation (presented at Princeton Plasma Phys...

Andrea Goulet

AI/ML Infra Meetup May. 23, 2024 Organized by Alluxio For more Alluxio Events: https://www.alluxio.io/events/ Speaker: - Eric Wang (Software Engineer, @Uber) Uber has numerous deep learning models, most of which are highly complex with many layers and a vast number of features. Understanding how these models work is challenging and demands significant resources to experiment with various training algorithms and feature sets. With ML explainability, the ML team aims to bring transparency to these models, helping to clarify their predictions and behavior. This transparency also assists the operations and legal teams in explaining the reasons behind specific prediction outcomes. In this talk, Eric Wang will discuss the methods Uber used for explaining deep learning models and how we integrated these methods into the Uber AI Michelangelo ecosystem to support offline explaining.

AI/ML Infra Meetup | ML explainability in Michelangelo

Alluxio, Inc.

AI/ML Infra Meetup May. 23, 2024 Organized by Alluxio For more Alluxio Events: https://www.alluxio.io/events/ Speaker: - Lu Qiu (Data & AI Platform Tech Lead, @Alluxio) - Siyuan Sheng (Senior Software Engineer, @Alluxio) Speed and efficiency are two requirements for the underlying infrastructure for machine learning model development. Data access can bottleneck end-to-end machine learning pipelines as training data volume grows and when large model files are more commonly used for serving. For instance, data loading can constitute nearly 80% of the total model training time, resulting in less than 30% GPU utilization. Also, loading large model files for deployment to production can be slow because of slow network or storage read operations. These challenges are prevalent when using popular frameworks like PyTorch, Ray, or HuggingFace, paired with cloud object storage solutions like S3 or GCS, or downloading models from the HuggingFace model hub. In this presentation, Lu and Siyuan will offer comprehensive insights into improving speed and GPU utilization for model training and serving. You will learn: - The data loading challenges hindering GPU utilization - The reference architecture for running PyTorch and Ray jobs while reading data from S3, with benchmark results of training ResNet50 and BERT - Real-world examples of boosting model performance and GPU utilization through optimized data access

AI/ML Infra Meetup | Improve Speed and GPU Utilization for Model Training & S...

Alluxio, Inc.

Migrating your customer service data from Zendesk to Re:amaze can significantly enhance your support operations, but it requires careful planning and execution. "A Guideline to Zendesk to Re:amaze Data Migration" is designed to assist businesses in managing this transition smoothly and efficiently. This comprehensive guide covers all aspects of the data migration process, ensuring that your data is transferred accurately and effectively.

A Guideline to Zendesk to Re:amaze Data Migration

Help Desk Migration

Top Mobile App Development Companies 2024

XongoLab Technologies LLP

IT Software Development Resume, Vaibhav jha 2024

vaibhav130304

How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?

XfilesPro

Agnieszka Andrzejewska - BIM School Course in Kraków

bim.edu.pl

Data privacy is one of the most critical issues that businesses face. This presentation shares insights on the principles and best practices for ensuring the resilience and security of your workload. Drawing on a real-life project from the HR industry, the various challenges will be demonstrated: data protection, self-healing, business continuity, security, and transparency of data processing. This systematized approach allowed to create a secure AWS cloud infrastructure that not only met strict compliance rules but also exceeded the client's expectations.

Designing for Privacy in Amazon Web Services

KrzysztofKkol1

INGKA DIGITAL: Linked Metadata by Design

Neo4j

Keynote at Sanae Beer.EX: The Automationist's Gambit

1. @maaretp http://maaretp.com The Automationist’s Gambit by Maaret Pyhäjärvi

2. @maaretp http://maaretp.com 2020 - historical film – 1 season

3. @maaretp http://maaretp.com Black cannot retain the pawn without incurring a disadvantage. White appears to sacrifice the c-pawn.

4. @maaretp http://maaretp.com The Automationist’s Gambit * Opening by sacrificing material to win in the end

5. @maaretp http://maaretp.com Time used on warning about test automation is away from succeeding with it. * opportunity cost

6. @maaretp http://maaretp.com Exploratory Testing TEST DESIGN TEST EXECUTION LEARNING, AGENCY IMPACTFUL RESULTS * power to decide with knowledge and attitude that goes with power

7. @maaretp http://maaretp.com Exploratory Testing? TEST DESIGN TEST EXECUTION MANUAL AUTOMATED

8. @maaretp http://maaretp.com Exploratory Testing? TEST DESIGN TEST EXECUTION MANUAL AUTOMATED

9. @maaretp http://maaretp.com Contemporary Exploratory Testing MANUAL AUTOMATED LEARNING, AGENCY IMPACTFUL RESULTS

10. @maaretp http://maaretp.com You can't automate well without exploring. You can't explore well without automating.

11. @maaretp http://maaretp.com An Example

12. @maaretp http://maaretp.com Algorithm Bug Test Cases Test data Openings

13. @maaretp http://maaretp.com Traditional Exploratory Testing Artifacts

14. @maaretp http://maaretp.com Test Strategy for E-Primer

15. @maaretp http://maaretp.com The Automationist’s Gambit Test Automation is Documentation!

16. @maaretp http://maaretp.com

17. @maaretp http://maaretp.com

18. @maaretp http://maaretp.com

19. @maaretp http://maaretp.com

20. @maaretp http://maaretp.com

21. @maaretp http://maaretp.com Single line àSee it fail àFirst test àSame test but variables àSame test but parameterized àFailing test with a bug àSpec to tests àGuess the values that are likely to fail àMultiple browsers à… àRuns in CI Throwaway automation?

22. @maaretp http://maaretp.com Bugs Found - Some of specified examples not properly recognized And Missed… - Text box resize is broken (my bad) - Browser crashes with 32k+1 chars with spaces (tool) - n and – and … messes up word count - More specified examples not properly recognized

23. @maaretp http://maaretp.com Automation in Frame of Exploratory Testing

24. @maaretp http://maaretp.com Attended Unattended Moving Focus Learning Learning Learning Learning

25. @maaretp http://maaretp.com UNIT SERVICE UI Exploratory Sprinkle On Top Exploratory Testing Contemporary Exploratory Testing UNIT SERVICE UI E x p l o r a t o r y

26. @maaretp http://maaretp.com Can You? Test Code Collaborate Ideate Learn

27. @maaretp http://maaretp.com

28. @maaretp http://maaretp.com

29. @maaretp http://maaretp.com Gambit is an opening with an appearance of sacrifice. What is your opening and what is your end game?

30. @maaretp http://maaretp.com 2020 2016 MIATPP Most Influential Agile Testing Professional Person #PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)

Keynote at Sanae Beer.EX: The Automationist's Gambit

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a Keynote at Sanae Beer.EX: The Automationist's Gambit

Semelhante a Keynote at Sanae Beer.EX: The Automationist's Gambit (13)

Mais de Maaret Pyhäjärvi

Mais de Maaret Pyhäjärvi (20)

Último

Último (20)

Keynote at Sanae Beer.EX: The Automationist's Gambit