Podcasts about Exploratory testing

These automated testing beliefs might be sabotaging your tests!In this episode, Nikolay debunks the seven biggest myths about automated testing. From the misconception that “more tests mean better quality” to the fallacy of “automation replacing manual testing,” Nikolay shares hands-on experiences and examples from his 16 years of experience. You'll learn how to optimize your automated tests, avoid costly mistakes, and streamline your testing processes for better efficiency and reliability.Whether you're a coding hobbyist or a seasoned pro, this episode is packed with insights for developers and companies alike to save time, money, and headaches – all while delivering smoother code.00:00) Intro(00:18) Myth #1: More Tests Mean Better Quality(01:02) 100,000 Automated Browser Tests and 40% Failure Rate(02:18) Single Test Strategy for CI Pipeline(03:53) Myth #2: Automation Replaces Manual Testing(05:14) Manual and Exploratory Testing(06:06) Myth #3: Automation is Too Expensive and Time-Consuming(07:55) Starting with a Single Test in CI(09:30) Myth #4: Anyone Can Write Automated Tests(11:40) Importance of Skilled Automation Engineers(12:46) Myth #5: Automation Tools Solve All Problems(14:30) Choosing the Right Tools for Salesforce Testing(16:45) Myth #6: All Tests Should Be Automated(18:44) Prioritizing Flows for Automation(19:26) Myth #7: You Can Set It and Forget It(21:07) Maintaining Automation SystemsCONNECT WITH NIKOLAY ADVOLODKIN          

In this episode of Arguing Agile, Brian and Om dive into the seedy reality of the "shadow backlog." Defined as all the hidden work and side projects that don't make it into the "official" backlog, shadow backlog items end up consuming significant time and effort from development teams. From personal passion projects to break fixes to exploratory work, we discuss the many forms the shadow backlog can take and how it impacts planning, productivity and team focus. Listen to  learn how to spot the signs of a growing shadow backlog in your own teams!agile, scrum, product management, backlog, sprint planning, technical debt, exploratory testing, side projects, passion projects, scope creep, team productivity = = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)= = = = = = = = = = = =AA171 - The Shadow Backlog: How Invisible Work Derails Your Teams

“The quality is connected to the risk, and the risk is connected to the testing. If we don't keep an eye on quality, our testing and development will drift, because we are no longer building the thing that people care about anymore." Mark Winteringham is a quality engineer and the author of “Testing Web APIs”. In this episode, discover how holistic, risk-based testing strategies can transform your software quality. Mark explains how to prioritize our testing by understanding what users truly value and translating that into different risk-based testing strategies, such as testing API design, exploratory testing, automated testing, and acceptance test-driven design (ATDD). Mark also reveals the testing Venn diagram as our testing strategic roadmap. Finally, get a glimpse of Mark's upcoming book “AI-Assisted Testing” and learn how AI will evolve the roles of testers and developers.   Listen out for: Career Journey - [00:01:24] Writing “Testing Web APIs” - [00:05:17] Holistic Testing Strategy - [00:07:48] Start With Understanding the Problem - [00:11:02] Testing Venn Diagram Model - [00:14:11] Risk-Based Testing - [00:18:22] Defining Quality & Quality Attributes - [00:22:29] Testing API Design - [00:26:41] Exploratory Testing - [00:32:08] Automated Testing - [00:36:18] Acceptance Test-Driven Design (ATDD) - [00:41:54] “AI-Assisted Testing” Book - [00:45:51] Evolution of Developer and Tester Roles - [00:48:46] 3 Tech Lead Wisdom - [00:53:51] _____ Mark Winteringham's BioMark Winteringham is a quality engineer, course director, and author of “AI Assisted Testing” and “Testing Web APIs”, with over 10 years of experience providing testing expertise on award-winning projects across a wide range of technology sectors. He is an advocate for modern risk-based testing practices, holistic based Automation strategies, Behaviour Driven Development and Exploratory testing techniques. Follow Mark: LinkedIn – linkedin.com/in/markwinteringham/ Twitter / X – @2bittester Website – mwtestconsultancy.co.uk _____ Our Sponsors Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 45% discount for Tech Lead Journal listeners by using the code techlead45 for all products in all formats. Like this episode? Show notes & transcript: techleadjournal.dev/episodes/172. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Buy me a coffee or become a patron.

In today's episode, I have the pleasure of sharing a presentation from Elisabeth Hendrickson, a renowned speaker, expert in test automation and development, and the author of the top-rated book Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing. I've been trying to get Elisabeth on the show since 2014 without any luck, BUT I hosted an online event, RoboCon, a few years ago where Elisabeth was the keynote speaker and thought now is my chance to at least create an episode featuring her by reusing her session here. Elisabeth's keynote speech titled "Robot Framework Through the Lens of History" will take you on a fascinating journey through the evolution of test automation, highlighting some lesser-known stories and influential figures along the way. As she delved into her archives, she discovered long-lost gems that shed light on the frustrations and challenges she encountered on her test automation journey. From the frustrations caused by heavyweight software development processes to the issues with test automation tools breaking and providing irrelevant information, Elisabeth takes us through the hurdles she faced, triumphs, and shares the history of test frameworks, including Robot Framework, along the way. You don't want to miss it. Listen up! Also, if you have anything to do with the Robot Framework, this is an excellent time to check out and register for RoboCon 24. They will have both an in-person and online version that I will be hosting. So go to testguild.com/robocon, register, and hope to see you there.

I was a core member of what Farrell would call a collaborative circle: the four people who codified Context-Driven Testing. That makes me think I can supplement Farrell's account with what it feels like to be inside a circle. I try to be "actionable", not just some guy writing a memoir.My topics are: what the context-driven circle was reacting against; the nature of the reaction and the resulting shared vision; how geographically-distributed circles work (including the first-wave feminist Ultras and the Freud/Fleiss collaboration); two meeting formats you may want to copy; why I value shared techniques over shared vision; how circles develop a shared tone and stereotyped reactions, not just a shared vision; and, the nature of “going public” with the vision. MentionedMichael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001.Cem Kaner, Jack Falk, and Hung Quoc Nguyen, Testing Computer Software, 1993.Édouard Manet, Le Déjeuner sur l'herbe (The Luncheon on the Grass), 1863.context-driven-testing.com (including the principles of context-driven testing), 2001?Cem Kaner, James Bach, Bret Pettichord, Lessons Learned in Software Testing: a Context-Driven Approach, 2002.Association for Software Testing.Elisabeth Hendrickson, Explore It! Reduce Risk and Increase Confidence with Exploratory Testing, 2012.Jonathan Bach, "Session-Based Test Management", 2000.Patrick O'Brian, Post Captain, 1972. (It's the second in a series that begins with Master and Commander.)Four articles that demonstrate personal style:James Bach, “Enough About Process, What We Need Are Heroes”, IEEE Software, March 1995.Brian Marick, "New Models for Test Development", 1999.Bret Pettichord, "Testers and Developers Think Differently", 2000.James Bach, "Explaining Testing to THEM", 2001.Los Altos Workshop on Software Testing and related:Cem Kaner, "Improving the Maintainability of Automated Test Suites", 1997. (This contains the conclusions of LAWST 1 as an appendix.)The LAWST Handbook (1999) and LAWST Format (1997?) describe the meeting format.The "Pattern Writers' Workshop" style is most fully explained in Richard P. Gabriel, Writers' Workshops & the Work of Making Things: Patterns, Poetry... (2002). James Coplien, "A Pattern Language for Writer's Workshops" (1997), describes writers' workshops in the "Alexandrian style" of pattern description (the one used in the seminal A Pattern Language). "Writers Workshop Guidelines" is a terse description.Image creditThe image is the painting Le Déjeuner sur l'herbe.

We are closing this cycle of Quality Sense with a very interesting guest... Maaret Pyhäjärvi, has more than 25 years of experience in software testing, and is constantly sharing her knowledge and helping others. She has experience organizing conferences around the world, meetups, and more. Maaret is currently working at Vaisala as a Principal Test Engineer. In today's episode, we talked about the challenges of organizing and attending conferences, and we dived into the topic of exploratory testing. How to define it, the challenges of building trust around exploratory testing, and more. So for the last time this year, get comfortable, grab a snack and enjoy!

In this episode, we are talking about the core of exploratory testing where we go in-depth on how exploratory testing going to be different from our day-to-day scripted testing, when & why we should use exploratory testing and more importantly the challenges we faced while practicing it. Host: Chamal Perera, Senior QA Lead, 99x Speakers: Vindhya Fernando, Quality Assurance Lead

GuestsElisabeth Hendrickson, @testobsessed, Curious Duck Digital LaboratoryChris McMahon, @chris_mcmahon, blogCitationsCrafting Science: A Sociohistory of the Quest for the Genetics of Cancer, Joan Fujimura, 1997. Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing, Elisabeth Hendrickson, 2012.

“Testing is an activity that happens throughout. It is not a phase that happens at the end. Start thinking about the risks at the very beginning, and how we are going to mitigate those with testing." Janet Gregory and Lisa Crispin are the co-authors of several books on Agile Testing and the co-founders of Agile Testing Fellowship. In this episode, Janet and Lisa shared the agile testing concept and mindset with an emphasis on the whole team approach, which was then followed by an explanation of the holistic testing concept with a complete walkthrough how we can use the approach in our product development cycle, including how Continuous Delivery fits into holistic testing. Janet and Lisa also described some important concepts in agile testing, such as the agile testing quadrants (to help classify our tests) and the power of three (aka the Three Amigos). Towards the end, Janet and Lisa also shared their perspective on exploratory testing and testing in production. Listen out for: Career Journey - [00:06:35] Agile Testing - [00:13:56] Whole Team - [00:15:17] Agile Testing Mindset - [00:19:19] Holistic Testing - [00:24:42] Continuous Delivery - [00:34:53] Agile Testing Quadrants - [00:39:03] The Power of Three - [00:42:50] Exploratory Testing - [00:47:08] Testing in Production - [00:50:49] 3 Tech Lead Wisdom - [00:54:10] _____ Follow Janet and Lisa: Janet's Website – https://janetgregory.ca Janet's Twitter – @janetgregoryca Janet's Linkedin – https://www.linkedin.com/in/janetgregory Lisa's Website – https://lisacrispin.com Lisa's Twitter – @lisacrispin Lisa's Linkedin – https://www.linkedin.com/in/lisa-crispin-88420a Agile Tester Blog – https://agiletester.ca/blog Agile Testing Fellowship Website – https://agiletestingfellow.com Our Sponsor Today's episode is proudly sponsored by Skills Matter, the global community and events platform for software professionals. Skills Matter is an easier way for technologists to grow their careers by connecting you and your peers with the best-in-class tech industry experts and communities. You get on-demand access to their latest content, thought leadership insights as well as the exciting schedule of tech events running across all time zones. Head on over to skillsmatter.com to become part of the tech community that matters most to you - it's free to join and easy to keep up with the latest tech trends. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/92.

In this episode we had AJ Wilson who is a Quality Engineer at Cazoo, stem advocate and community champion. We chatted about attending my contract testing workshop as a novice, including API maintenance regularly, exploring API's, observability, reviewing conference abstracts for Grace Hopper Conference, empowering women in tech through mentoring and much more. You can follow @AjParadith on Twitter or connect with her on LinkedIn. Hosted on Acast. See acast.com/privacy for more information.

As you test, are you learning? Does each test impact the design of the next test? As you test, is a group learning? Is the wisdom of the crowd continuously used to inspect and adapt the testing approach? Join Chris and Austin as they discuss Ensemble Teaching, Exploratory Testing, and Product Development with Maaret Pyhäjärvi. She not only shares about exploratory testing before and after ensembling, but also about the synergy of visualization and exploratory testing. Lastly she shares about ensemble programming with kids, students, and women over 40.  Video and Show Notes: https://youtu.be/AjJF-0r5HMc  

Exploratory testing is absolutely an essential part of a testing strategy. This episode discusses what exploratory testing is, its benefits, and how it fits within a framework of relying on automated tests for most of our testing.

In this Agile Podcast, Brian Orlando and Om Patel discuss User Acceptance Testing. Is it necessary in Agile Software Development and if it is, what should it look like in Agile Software Development?0:00 Topic Intro0:28 Is it Needed?5:52 Exploratory Testing for Confidence7:53 Typical Testers "Owned" by Development10:23 Who is Involved?12:15 Responsibility/Accountability for the UAT16:49 Roadmaps and UAT19:50 Rolling UAT into DoD21:21 Design Thinking UAT23:12 Isn't This Roadmap Item Just a Gantt Chart?24:21 Marrying the Incremental with the Whole25:38 Personas to Accelerate UAT27:57 Risk of User Personas - Silo'd Thinking34:20 UAT Expectations & Metrics37:07 Brainstorming for Metrics39:14 Escaped Defects, Business Value, Missed Opportunity41:45 Measuring Stupid Things43:47 Better UAT Metrics45:40 Arbitrary Metrics and Deadlines47:09 UAT Triage51:01 Product Manager/Owner Quagmire53:08 Best UAT Story55:18 Include the Right People56:55 One Last Talk on Metrics59:50 Wrap-Up= = = = = = = = = = = = Also available on YouTube:https://www.youtube.com/watch?v=uRZ5dWtNyfQPlease Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1= = = = = = = = = = = = Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xNzgxMzE5LnJzcwSpotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-PodcastStitcher:https://www.stitcher.com/show/agile-podcast-2= = = = = = = = = = = = Agile Podcast 30 - User Acceptance Testing in Agile

Welcome to episode 22 of the Testing Peers podcast. This week the Peers tackle exploratory testing.After the important check-in on David's potato harvest, Simon asks us if our curiosity has ever led to us breaking anything – which eventually leads us to the main event.What do we mean by exploratory testing?How does it differ from ad-hoc testing?What skills are required?How can we tackle the KPI/Metrics conversation?Have we been exploratory testing without explicitly calling it that?The Peers mention a lot of really useful resources as well:Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing – Elisabeth HendricksonExploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design – James WhittakerExploratory Testing with the Team, a Journey Worth Taking – Maaike BrinkhofFive Years of Mob Testing, Hello to Ensemble Testing – Maaret PyhäjärviTestBuddy – Simon TomesA new model for test strategies… (An update to the Heuristic Test Strategy Model) – Dan AshbyWe really appreciate all the feedback that we have received and invite you to get in touch with us:ContactUs@TestingPeers.comTwitter (https://twitter.com/testingpeers)LinkedIn (https://www.linkedin.com/company/testing-peers)Instagram (https://www.instagram.com/testingpeers/)Facebook (https://www.facebook.com/TestingPeers)If you like what we do and are able to, please visit our Patreon to explore how you could support us going forwards: https://www.patreon.com/testingpeersSaffron QA is a provider of recruitment and consultancy services, exclusively for the software testing industry.You can find out more at https://saffronqa.co.uk/  or on LinkedIn at https://www.linkedin.com/company/saffron-qa/We've found Ben from Saffron QA to be a great partner who has signed up to the vision and values that we have set out in our Testing Peers charter and we hope that you will take the time to visit and connect with him.Support the show (https://www.patreon.com/testingpeers)

Many of us are familiar with the idea of negative testing, where we feed bad data or inputs to a program or application to see how it behaves. That works for a program or an app but how about an entire infrastructure? A discipline that has come to be known as Chaos Engineering is where this level of "testing" comes into play. Intriguing but what is "Chaos Engineering?" Claire Moss joins Matt Heusser and Michael Larsen to discuss the good, bad, ugly, and just plain odd aspects of a discipline that is not readily understood but bears a resemblance to Exploratory Testing. It is also available to any organization that wants to implement it, provided they are ready and willing to go down a rabbit hole or ten.

In this podcast recorded at Agile 2019, Shane Hastie, Lead Editor for Culture & Methods, spoke to Lanette Creamer about the need for technical skills by testers and the importance of exploratory testing. Why listen to this podcast: • Despite the importance and value it provides, software testing is not a particularly respected profession • Testers with development skills and developers with testing skills can communicate effectively with each other and pairing results in faster bug identification and removal • Unit tests are an asset of confidence • Testers have an ethical responsibility to think beyond the intended use of the code, considering what could happen and how the product could be misused • Exploratory testing is an approach where instead of trying to prove that the software works, the goal is discovery More on this: Quick scan our curated show notes on InfoQ https://bit.ly/3hQAiuP You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/3hQAiuP

In the second installment of The Idealcast’s Dispatch From the Scenius series, Gene Kim explores Elisabeth Hendrickson’s 2015 and 2014 DevOps Enterprise Summit presentations. Listen as Gene breaks down Hendrickson’s experience and learnings, all to help you find fundamental principles to apply to immediately keep your feedback cycles healthy and happy. In this episode, Hendrickson, an experienced QA engineer, shares her realization that the better she got at her job, the worse she made things for the organization as a whole. Thus began her journey to uncover the relationship between testing and quality, which has led her to a reality of increasingly tight feedback loops. Episode Timeline: [00:00] Intro [00:22] Meet Elisabeth Hendrickson and her DevOps Enterprise Summit Presentation [01:02] Elisabeth’s presentation intro [02:02] Silicon Valley 1999 [05:43] Quality is getting worse [06:42] Steamer round table and System of Effects Diagram [07:54] Theory: Increase quality by throwing more testers at the problem [08:49]The existence of QA created more bugs [10:20] Feedback Cycles [15:01] Shrodinger’s Cat and Fragile not Agile [18:43] Creating visibility around Feedback Cycles [26:19] Kolb’s learning cycle [28:03] How team’s branch and merge [32:20] Polluted feedback [33:40]WordCount Simulation [36:33] Better visibility [37:42] Takeaways [40:56] The illusion of speed over real progress [47:11] Outro  ABOUT THE GUESTS Elisabeth Hendrickson is a leader in software engineering. She most recently served as VP R&D for Pivotal Software, Inc. A lifelong learner, she has spent time in every facet of software development, from project management to design for companies ranging from small start-ups to multinational software vendors. She has helped organizations build software in a more efficient way and pioneered a new way to think about achieving quality outcomes and how that hinges on fast and effective feedback loops. Her book, Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing, was released in 2013 and explores technical excellence and mastery, and creating effective feedback loops for everyone. She spoke at the DevOps Enterprise Summit in 2014, 2015, and 2018, and received the Gordon Pask Award from the Agile Alliance in 2010. Visit Elisabeth’s website Twitter LinkedIn   YOU’LL LEARN ABOUT Feedback loops. Feedback and opinion are different things. Beware of polluted feedback streams. WordCount simulation. Fighting feedback entropy takes enormous energy. Meetings are easy; getting real work done is hard. Tools and test frameworks are foundational: the devs who build them have to be better than average. Becoming a learning organization. RESOURCES It's All About Feedback, Elisabeth Hendrickson’s 2015 DevOps Enterprise Summit presentation video. On the Care and Feeding of Feedback Cycles, Elisabeth Hendrickson’s 2014 DevOps Enterprise Summit presentation video. On the Care and Feeding of Feedback Cycles slide deck. It’s All About Feedback slide deck. Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing by Elisabeth Hendrickson “Let a thousand flowers bloom. Then rip 999 of them out by the roots.” Gigamonkeys. The WordCount Simulation by Elisabeth Hendrickson.  

In Episode 3, Gene Kim is joined by Elisabeth Hendrickson, who inspired many ideas in The DevOps Handbook and, more recently, The Unicorn Project. She has shaped the way Gene sees the world of DevOps. From Developer to Tester ratios, to the importance of architecture, and the need for leaders to decompose systems well. Together they explore her years as VP R&D for Pivotal Software, Inc., software development, and the link between organizations and architecture. In a wide-ranging discussion, they cover Elisabeth’s mental model of balance, structure, and flow, to her view of how organizations really work. Listen as Gene and Elisabeth explore her WordCount Simulation, to her personal experience with MIT’s Beer Game, and much more.   ABOUT THE GUESTS Elisabeth Hendrickson is a leader in software engineering. She most recently served as VP R&D for Pivotal Software, Inc. A lifelong learner, she has spent time in every facet of software development, from project management to design for companies ranging from small start-ups to multinational software vendors. She has helped organizations build software in a more efficient way and pioneered a new way to think about achieving quality outcomes and how that hinges on fast and effective feedback loops. Her book, Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing, was released in 2013 and is explores technical excellence and mastery, and creating effective feedback loops for everyone. She spoke at the DevOps Enterprise Summit in 2014, 2015, and 2018, and received the Gordon Pask Award from the Agile Alliance in 2010. Visit Elisabeth’s website Twitter LinkedIn   YOU’LL LEARN ABOUT How to build software in a more efficient way Elisabeth’s mental model of balance, structure and flow How Conway’s law applies to Elisabeth’s model Elisabeth’s WordCount Simulation    Episode Timeline: [00:09] Intro [00:15] Meet Elisabeth Hendrickson [04:14] “Better Testing - Worst Quality?” [04:54] “Managing the Proportion of Testers to (Other) Developers” [08:25] How to get great testing behaviors [13:29] How structure enables developers to work on features [16:08] Applying principle to non-functional requirements [18:43] Conway’s law and Inverse Conway Maneuver [27:43] Elisabeth’s model on balance, structure and flow [31:01] MIT’s Beer Game [36:41] The WordCount Simulation [44:54] Becoming a good partner [50:03] Drawing lines as a leader [55:39] The Five Ideals [57:33] Stuck in a cost center [1:05:44] It’s all about feedback [1:10:50] The Phoenix Project’s Sarah’s background [1:19:09] Who is your first team? [1:28:07] Finding Elisabeth Hendrickson [1:28:29] Outro   RESOURCES Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity by Kim Scott The four quadrants of Radical Candor Ruinous Empathy Manipulative Insincerity Obnoxious Aggression Radical Candor Dangerous Company: The Consulting Powerhouses and the Businesses They Save and Ruin by James O’Shea Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing by Elisabeth Hendrickson Better Testing, Worse Quality? by Elisabeth Hendrickson  Managing Proportions of Testing to (Other) Developers by Dr. Cern Kaner, Elisabeth Hendrickson, and Jennifer Smith-Brok When NASA Lost a Spacecraft Due to a Metric Math Mistake by Ajay Harish Lockheed: New Carrier Hook for F-35 by Dave Majumdar Conway's law Decoding the DNA of the Toyota Production System by Steven Spear and H. Kent Bowen The WordCount Simulation by Elisabeth Hendrickson "The Beer Game" by Prof. John D. Sterman

#Live2Test Podcast Series continues with our 3rd session. This time we have hosted Olivier Denoo, the president of ISTQB.

Episode 43 of the Modern Agile Show features an interview with Maaret Pyhäjärvi (@maaretp), a Lead Quality Engineer at FSecure, an agile practitioner and the author of Strong Style Pair Programming, Mob Programming Guidebook and Exploratory Testing. Maaret describes the culture at FSecure and the benefits her team discovered when they experimented with removing the Product Owner from their team (though there is still a Product Management group in the company). Her team found that the benefits included far greater productivity, solving problems they hadn't managed to solve in years and becoming far more data-driven. Maaret describes the “superpower” have having a “feature team” that works across three different technical stacks, and how #NoProductOwner, #NoEstimates and #NoJira are working nicely. She describes how her teams have shortened releases from every six months to every two weeks. Maaret's team runs about 300,000 automated tests everyday on 14,000 virtual machines. Only a few of the FSecure developers use Test-Driven Development. The company also got rid of all Scrum Masters during a resizing. Coaching happens, yet it's not an official title. Maaret is a fan of the Modern Agile principles and uses them in her work. You can learn more about Maaret and her work at https://maaretp.com/

Episode 40 of the Modern Agile Show features an interview with Elisabeth Hendrickson, a veteran tester, developer, agilist, trainer, author and former executive of Research and Development at Pivotal. We discuss how Elisabeth first got into agile development and what a paradigm shift Extreme Programming (XP) was for her. We discuss her definition of agile and how she has applied agile principles to her work. We discuss how the testing community first reacted to practices like Test-Driven Development. We also discuss Exploratory Testing, the impact it's had on agile development and Elisabeth's book on the subject, called Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing.

Exploratory testing is a name given for a technique of using knowledge, experience, and skills to test software in a non-linear, investigatory fashion. Is it a powerful and important part of each professional tester’s repertoire, or actually magic quality pixie dust? Is this the only real way of testing, or is there room for other forms of validation as well as verification? What are the origins of exploratory testing, and who actually invented the technique (as opposed to coining the current name)? Does it always degrade into an unmanageable, unaccountable, random bug hunt, or are there ways to instill order, measure coverage, and build confidence with it? In this webinar, Rex will explore and burst some of the myths of exploratory testing.

There is an approach to testing called Exploratory Testing and it is important to know how to use it, when to use it, how to manage it, what are its strengths and some of its weaknesses and we want to talk about this today

GUEST BIO: Maaret Pyhajarvi is an Engineering Manager for F-Secure leading a team while continuing with hands-on testing and programming.   In 2016, Maaret was awarded Most Influential Agile Testing Professional Person and she has spoken at events in 25 countries delivering close to 400 sessions.  Maaret is also author of two books, Mob Programming Guidebook and Exploratory Testing.   EPISODE DESCRIPTION: Phil’s guest on today’s show is Maaret Pyhajarvi. She is an Eng Manager, Tester, Polyglot Programmer, Conference Designer, Speaker and Author. For the past 25 years she has mainly worked in the testing field and has written two books on the subject. Her Mob Programming Guidebook and Exploratory Testing books are both very well regarded. Maaret received the Most Influential Agile Testing Professional Person award, in 2016. She is a well-known conference speaker, who has delivered close to 400 sessions, in 25 countries. KEY TAKEAWAYS: (1.10) – So Maaret, can I ask you to expand on that brief intro and tell us a little bit more about yourself? Maaret explains that she has been working in the IT testing field, for about 25 years. But, it is only in the past couple of years that she has thought about and started to understand what motivates her and the role she is fulfilling in this industry. After someone who did not work in the industry asked her what she did for a living she realized that she is actually a feedback fairy. In other words, she finds problems and shares them with the developers in a way that enables them to fix the issue. Something that end-users cannot do, they can only really highlight problems, but do not have the tech knowledge to come up with possible solutions. (2.14) – Can you please share a unique career tip with the I.T. career audience? Maaret’s advice is to remember that you can craft any job you are given into the job you want. Over the years, she has been crafting the way she works to better suit each of the companies she works with. Maaret likes to over deliver, to push the boundaries. People are often surprised by the tasks she carries out. They do not identify some of these things as being tester related. This is evidence that Maaret has been crafting her role into something that better suits her and provides the firms she works for with extra benefits. Phil asks her if she brings her personal values to her work. Maaret agrees that this is very much the case. In fact, she has changed the way she works so much that when she took on a management job just 6 months ago, she realized she had been basically filling that role for some time. If there is a job to do that she knows she is going to enjoy Maaret will usually volunteer or take the initiative and just get it done. It is not always necessary to ask for permission. You just need to be ready to apologize later if you misinterpret what needs to be done. But, usually, you get it right, so apologies are not needed. (4.08) – Can you tell us about your worst career moment? And what you learned from that experience. That happened about 10 years ago. She was working as a contractor on the customer organization side and had overall responsibility for a multi-million euro project. Normally, she would have taken a hands-on approach. But, her then manager asked her to do things differently. They wanted her to focus on the metrics. She was assigned with tracking, preparing and explaining the progress of testing, at boardroom level. Helping the board to understand where the quality was bad, basically, preparing for these discussions. Naturally, that is what she did, barely touching the application itself. The system they were developing and testing had multiple customers. So, usually there were two other big contractors, representing two other user clients in the boardroom with her. One day, when a big decision was about to be made, at the door of the meeting room, these two people told her they could not come into the meeting. They said they were working for other clients who were considered to be direct competitors of this board’s firm. So, because of a conflict of interest they had to stay outside. This left Maaret handling the meeting. At the time, there were serious quality issues and a key decision had to be made. Naturally, Maaret struggled to explain things to the board at what was a critical point for the project. She had very little hands-on knowledge of the system and was thrown in at the deep end, at the very last moment. Unsurprisingly, the outcome of that meeting was not good. She was unable to win the argument, which resulted in her company losing a huge amount of money. For Maaret this was a real career low. (7.18) – What was your best career moment? Maaret is lucky enough to work in a fast-moving field, which provides her with career highlights on a regular basis. But, one of her biggest highlights was helping one of the companies she worked for to reduce their end-user problem rate. When she joined them their issue rate was 18%, which, by any standards, is extremely high. At the time, they were releasing every few weeks. Each time things were getting done at the very last minute. A chaotic way of working, so, unsurprisingly issues were still slipping through. In an effort to tackle this issue, they decided to move to daily releases, which really helped. Speeding up the process meant they were introducing smaller changes that were easier to test and track. As a result, there were far fewer end-user issues. Plus, if anything small slipped through it could usually be fixed very quickly. This speeded up release process meant that there was not enough time for problems to accumulate and become big enough to cause serious issues for end users. It is a way of working that she has introduced to her current company. Working like this is far better than waiting weeks, even months for a release. Something Maaret is quite relieved about.  She finds that having to work on a project for 6 months before a release drives her insane. (11.08) – Can you tell us what excites you about the future of the IT industry and careers? The fact that the work she does has a big impact on people’s lives excites Maaret. These days, it is easier to work in a way that makes sure that what you create really does fill a need. She is also excited by the potential of today’s machine learning related technologies. Being able to work so much faster opens up a world of possibilities, things that were once impossible are now possible, easy even. (12.16) – What drew you to a career in IT? Maaret explained that she had wanted to become a chemist. But, she suffered from allergies. Her doctor advised her that working as a chemist would be too dangerous. So, Maaret looked into other possibilities and came across software development. The people involved in the industry seemed to be really nice and she enjoyed creating something useful while working in a team. (12.56) – What is the best career advice you have ever received? One of her bosses once reminded her that she did not have to be perfect. This was very good advice for Maaret. At the time, she was holding herself to a crazy high standard. So much so, that, at one stage, she felt like a complete failure. Fortunately, her boss helped her to realize that perfection is not necessary or expected. They showed her that she did add value and was good at her job. (13.19) – If you were to begin your IT career again, right now, what would you do? Maaret says she would probably follow the same career path. But, she would work differently. Instead of starting the testing process slowly using case studies, she advocates jumping straight into exploratory testing. In fact, she is now teaching 17-year-olds to work in that way. (14.01) – What are you currently focusing on in your career? Right now, Maaret is figuring out how to multiply the impact of the R&D team by making them feel responsible without the presence of a product owner. (14.17) – What is the number one non-technical skill that has helped you the most in your IT career? Over the years, Maaret has developed the ability to break down illusions. To help others, and herself, to break free of conventional thinking and try to do things differently. To the extent that sometimes it is a good idea to try something even when you are fairly sure it will not work. Exploring all avenues is the best way to discover new things. (14.46) – Phil asks Maaret to share a final piece of career advice with the audience. Her advice is to pay attention to your impact. You need to be hands-on and do some of the work. But, you should also be generative, helping others to multiply their impact. BEST MOMENTS: (2.25) MAARET – "Remember is that you can craft any job you're given into the job you want to have" (12.47) MAARET – "That feeling of achieving something in a in a group of people is will really draw me in and keeps drawing me in still." (14.27) MAARET – "Sometimes telling yourself to try things that you are sure don't work is the best thing you can do" (14.48) MAARET – “Pay attention to your impact.”   CONTACT MAARET: Twitter: https://twitter.com/maaretp LinkedIn: https://www.linkedin.com/in/maaret/ Website: http://maaretp.com Blog: http://visible-quality.blogspot.fi

Once you have a bunch of great ideas from your reflection, how can you make sure you and your team actually use what you've learnt? We illustrate several variations on one of our favourite learning-capture methods, the humble checklist - including self-improving lists and an idea that survived ten years by migrating among multiple checklist formats, from wiki page to slackbot. SHOW LINKS: - The Checklist Manifesto: https://en.wikipedia.org/wiki/The_Checklist_Manifesto - Jeffrey's Glider Training Video: https://www.youtube.com/watch?v=s6QcOQ3olbE - Elizabeth Hendrickson's Testing Cheat Sheet: http://testobsessed.com/2007/02/test-heuristics-cheat-sheet/ - Making Software Like Intensive Care or Bombing Missions: https://blog.jeffreyfredrick.com/2008/09/10/making-software-like-intensive-care-or-bombing-missions/ - Exploratory Testing: https://en.wikipedia.org/wiki/Exploratory_testing - Human in the Loop: https://en.wikipedia.org/wiki/Human-in-the-loop *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

In this podcast, testing expert Matt Heusser explains how exploratory and scripted tests differ and how they complement each other.

In this podcast, testing expert Matt Heusser explains how exploratory and scripted tests differ and how they complement each other.

Dr. Marcia Buzzella and Susan Zampino join us on this week's episode to discuss the need for testers to "know their audience" when trying to convey the importance of exploratory testing. We hear all the time about the need for testers to continuously sharpen their testing skills, but how often do their social or communication skills get the same attention?

This episode is a real treat! Mike Lyles spends time with Nancy Kelln, a test manager with 16 years of diverse IT experience. Nancy and Mike discuss how to implement Exploratory Testing into your organization and what's behind the name of her session "What the Hell Kind of Testing Is That?"Learn More about Nancy Kelln:http://www.stpcon.com/speakers/nancy-kelln/

This episode is a real treat! Mike Lyles spends time with Nancy Kelln, a test manager with 16 years of diverse IT experience. Nancy and Mike discuss how to implement Exploratory Testing into your organization and what's behind the name of her session "What the Hell Kind of Testing Is That?"Learn More about Nancy Kelln:http://www.stpcon.com/speakers/nancy-kelln/

Maaret Pyhäjärvi traveled from her native Finland to speak at the Agile Alliance Technical Conference 2016 about "Exploratory Testing in API". According to Maaret, much of what's keeping non-technical people from understanding development and testing is not having a GUI to interact with and explore. "I wanted to create an experience ... where we actually take some API, which looks like code and doesn't have a user interface" and create a GUI for individuals to do exploratory testing on. In this session she applies her 20 years of experience in testing and, more recently, mob testing to enable non-developers to participate in exploratory testing in a mob development environment.  Maaret Pyhäjärvi is a software specialist with emphasis on testing. She works with a 10-person software development team at Granlund Oy as the testing specialist. On the side, she delivers hands-on testing trainings and consults on testing through Altom Consulting Oy. SolutionsIQ's Neville Poole hosts. About Agile Amped The Agile Amped podcast series engages with industry thought leaders at Agile events across the country to bring valuable content to subscribers anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter Like: http://bit.ly/SIQFacebook

Upcoming Philly Area Events June 20 – Old City, Philadelphia – Ken Rimple @ LibertyJS doing an AngularJS for beginners workshop in the AM June 18 – Agile Philly – Strafford, PA – Exploratory Testing for Mobile Devices June 24 – Agile Philly – Center City, Philadelphia – Agile Transitions June 18 – CocoaHeads – ... Read More The post DevNews #100 – Strap on your tin foil hats, it’s our 100th show! appeared first on Chariot Solutions.

Panel David J. Soler (twitter blog) Curtis McHale (twitter github blog) Eric Davis (twitter github blog) Jeff Schoolcraft (twitter github blog) Reuven Lerner (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:04 - David J. Soler Introduction Relationship Marketing & Sales Podcast davidjsoler.com 01:54 - Building Relationships and Getting Referrals Trust, Likability, Credibility + Value (TLC+V) Handwritten, Personal Notes 13:39 - Trust Integrity Reputation Consistency 23:52 - Unconventional Marketing ‘Wow' Factor Before, During, and After Items of Value 30:11 - Referrals 32:10 - Meet Your Clients 34:31 - Appreciation and Encouragement 36:37 - Relationships Over Business Picks Thou Shall Prosper: Ten Commandments for Making Money by Rabbi Daniel Lappin (Curtis) Ladda Buttons (Curtis) Freelancing Rules of Thumb (Eric) Apple Developer: for WWDC Videos (Jeff) Mac Pro (Jeff) httpie (Reuven) Reversing PDF Documents (Reuven) Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing by Elisabeth Hendrickson (Chuck) The Compound Effect by Darren Hardy (David) Next Week Freelancers Show: LinkedIn with Wayne Breitbarth Transcript DAVID: Are we live on the show? Are we broadcasting...or just setting up? CHUCK: I'm just doing some quick sound checks and then we'll get going... DAVID: Okay, great! CHUCK: Which is just me watching the volume meter while everybody talks. So, go ahead. REUVEN: Ohh! Is that what secretly happens? [laughter] REUVEN: And here I thought you're just trying to get us to be friendly. [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net.] CHUCK: Hey everybody and welcome to Episode 66 of The Freelancers Show! This week on our panel, we have Curtis McHale. CURTIS: Good morning! CHUCK: Eric Davis. ERIC: Hello! CHUCK: Jeff Schoolcraft. JEFF: What's up! CHUCK: Reuven Lerner is trying to connect. I guess the wiring in Atlantic Ocean got cut; somebody wrong it over or something. I'm Charles Max Wood from DevChat.tv. This week, we have a special guest and that's David J. Soler. DAVID: Hello everybody! Thanks for having me! CHUCK: No problem. Do you want to introduce yourself really quickly? DAVID: Sure! My name is David J. Soler, I am the host of the Relationship Marketing and Sales Podcast. You can learn more about me at davidjsoler.com. I am here to share and answer new questions that I can that you guys want to ask! CHUCK: Awesome! Now, I know David because we're in the same Mastermind Group, so we talk twice a month and he has helped me with quite a bit of marketing stuff. The thing that really kind of got me excited about getting you on the call besides your podcast, which is awesome, you've had some great guests, too. I think my favorite is the one with David Siteman Garland. DAVID: Yeah, it was blast. He's just a real smart guy, online entrepreneur, and just lot of great helpful tips. I'm glad you enjoyed it. It's been a blast to interview people like him. CHUCK: Yeah. Anyway, you did something that was a little bit kind of outside the box that got me thinking, so I thought we'd bring that on and have you talk to us a little bit about some of the, I guess, less conventional things that you do. What you did was you sent 'Thank You' cards out to everybody in our Mastermind Group. I have to say, I don't usually get Pay-Per-Mail unless it's Pay-Per-Mail that says, "You owe us money." [David chuckles] CHUCK: So, I thought that was interesting! I was just wondering, what other ideas or techniques or ways of coming up with things like that, that we could do in our freelancing businesses to kind of make a  connection? DAVID: Sure, definitely! Well, the thing about it and approach that I'm trying to take you say unconventional, really,

Panel David J. Soler (twitter blog) Curtis McHale (twitter github blog) Eric Davis (twitter github blog) Jeff Schoolcraft (twitter github blog) Reuven Lerner (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:04 - David J. Soler Introduction Relationship Marketing & Sales Podcast davidjsoler.com 01:54 - Building Relationships and Getting Referrals Trust, Likability, Credibility + Value (TLC+V) Handwritten, Personal Notes 13:39 - Trust Integrity Reputation Consistency 23:52 - Unconventional Marketing ‘Wow’ Factor Before, During, and After Items of Value 30:11 - Referrals 32:10 - Meet Your Clients 34:31 - Appreciation and Encouragement 36:37 - Relationships Over Business Picks Thou Shall Prosper: Ten Commandments for Making Money by Rabbi Daniel Lappin (Curtis) Ladda Buttons (Curtis) Freelancing Rules of Thumb (Eric) Apple Developer: for WWDC Videos (Jeff) Mac Pro (Jeff) httpie (Reuven) Reversing PDF Documents (Reuven) Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing by Elisabeth Hendrickson (Chuck) The Compound Effect by Darren Hardy (David) Next Week Freelancers Show: LinkedIn with Wayne Breitbarth Transcript DAVID: Are we live on the show? Are we broadcasting...or just setting up? CHUCK: I'm just doing some quick sound checks and then we'll get going... DAVID: Okay, great! CHUCK: Which is just me watching the volume meter while everybody talks. So, go ahead. REUVEN: Ohh! Is that what secretly happens? [laughter] REUVEN: And here I thought you're just trying to get us to be friendly. [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net.] CHUCK: Hey everybody and welcome to Episode 66 of The Freelancers Show! This week on our panel, we have Curtis McHale. CURTIS: Good morning! CHUCK: Eric Davis. ERIC: Hello! CHUCK: Jeff Schoolcraft. JEFF: What's up! CHUCK: Reuven Lerner is trying to connect. I guess the wiring in Atlantic Ocean got cut; somebody wrong it over or something. I'm Charles Max Wood from DevChat.tv. This week, we have a special guest and that's David J. Soler. DAVID: Hello everybody! Thanks for having me! CHUCK: No problem. Do you want to introduce yourself really quickly? DAVID: Sure! My name is David J. Soler, I am the host of the Relationship Marketing and Sales Podcast. You can learn more about me at davidjsoler.com. I am here to share and answer new questions that I can that you guys want to ask! CHUCK: Awesome! Now, I know David because we're in the same Mastermind Group, so we talk twice a month and he has helped me with quite a bit of marketing stuff. The thing that really kind of got me excited about getting you on the call besides your podcast, which is awesome, you've had some great guests, too. I think my favorite is the one with David Siteman Garland. DAVID: Yeah, it was blast. He's just a real smart guy, online entrepreneur, and just lot of great helpful tips. I'm glad you enjoyed it. It's been a blast to interview people like him. CHUCK: Yeah. Anyway, you did something that was a little bit kind of outside the box that got me thinking, so I thought we'd bring that on and have you talk to us a little bit about some of the, I guess, less conventional things that you do. What you did was you sent 'Thank You' cards out to everybody in our Mastermind Group. I have to say, I don't usually get Pay-Per-Mail unless it's Pay-Per-Mail that says, "You owe us money." [David chuckles] CHUCK: So, I thought that was interesting! I was just wondering, what other ideas or techniques or ways of coming up with things like that, that we could do in our freelancing businesses to kind of make a  connection? DAVID: Sure, definitely! Well, the thing about it and approach that I'm trying to take you say unconventional, really,

Serge Lucio, IBM Rational, introduces listeners to James Whittaker, Test Director of Google and Thought Leader, as he shares his thoughts on how the world of software testing is changing, how Google is moving forward adopting change, and how IBM is moving forward to embrace this change.