Podcasts about behaviour driven development

“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 dieser Folge des Sandpapier unterhalten sich Theo, Florian und Tobias über Qualitätsverbesserungen. Was haben wir im vergangenen Jahr verändert, welche Experimente haben wir gestartet und was haben wir daraus gelernt? Wir gehen auf die Themen Code Reviews, Pair Programming, Testing und Test Driven Development sowie Behaviour Driven Development, Code-Kommentare und Konzeption ein. Theo und Florian berichten aus ihrer täglichen Projektpraxis, von Lern-Momenten und Themen, die sie als nächstes auf der Agenda haben. Als Ausblick schneiden wir das Thema statische Codeanalyse an. Ein spannender Streifzug durch unseren Programmieralltag mit dem ein oder anderen Blick unter den Teppich. Diese Themen haben wir angesprochen: Shape Up von Basecamp BDD in Action Sustainable Software Sandstorm Meetingkultur - Sandpapier Folge 24 Falls ihr Fragen oder Anregungen habt, immer her damit: Theo auf Twitter: @on3iro Florian im Fediverse: @lauchgott Tobias auf Twitter: @sandstorm_tobi Sandstorm auf Twitter: @sandstormmedia Sandstorm auf Instagram: sandstormmedia Oder schreibt uns eine Mail an kontakt@sandstorm.de Das Sandpapier ist der regelmäßig unregelmäßige Podcast der Sandstorm Media GmbH. Wir erzählen aus unserem Alltag, was wir versuchen, anders zu machen und welchen Herausforderungen und Experimenten wir uns auf unserem Weg stellen.

What is Behaviour-Driven Development? How can it be used to benefit the whole product team? How do you rubberduck? What are the secrets to writing great documentation ? On this episode of the Glowing in Tech podcast, we are joined by the one and only Tanya Powell who works as a co-CTO at Coding Black Females. She shares her tech topic in tech which is all about behaviour driven development, and her controversial take on bad documentation. Show notes for the episode including timestamps and how to get in touch with us and our guests, all here: https://www.notion.so/Episode-10-Tanya-Powell-Part-2-fde7803f70bb488886f9a72805f0f920 Stay up to date by following us on our socials: Instagram: https://www.instagram.com/glowingintech Twitter: https://www.twitter.com/glowingintech Support/Advertise with us: https://forms.gle/eLMUST2puKzuA25c7 --- Send in a voice message: https://anchor.fm/glowing-in-tech/message

In this month's episode we talk about Behaviour Driven Development (BDD), a testing practice where system behaviours are captured in a human readable Domain Specific Language (DSL), which are automated and executed. Colin is joined by colleagues Daniel McNamee, Xin Chen and Jack Arnstein who bring their many years of testing experience to a lively debate on this topic. They discuss the essence of BDD: is it the DSL, the automation frameworks, or is it more simply the conversations that take place as part of writing these scenarios/feature files? There are also limitations to BDD, so they discuss when it provides value, and when it might not. And they consider the question ‘just how expensive is it as an approach?'. Finally, they wrap up by considering whether BDD is simply misunderstood. Links from the podcast: Introducing BDD – Dan North The Tragedy of Given-When-Then – Chris Matts The Three Amigos The Value at the Intersection of TDD, DDD, and BDD – Darshan Satya

Materiały dodatkowe:Składnia języka GherkinCucumberJBehaveSpecFlowBehatThoughtworks GaugeThoughtworks TaikoDodatkowo, sporo ciekawych odnośników do materiałów związanych z Behaviour-Driven Development znajduje się z repozytorium Mateusza, Awesome-BDD

Liz Keogh: How to start Making Sense & Salt Marshes …with examples. Blogger, Coach, Speaker, Liz is well known for her enthusiasm for moving the Lean & Agile movement onwards.Starting the first 3 years of her career on a project that never finished its first release, her view of the world rapidly changed joining Thoughtworks where code was with client within 4 weeks. She joined them as Behaviour-Driven Development was emerging and Liz gives an expert breakdown of what BDD is, the value it brings to the business and how to practice it well. And then on to Cynefin which Liz describes as a framework for making sense of the world, particularly in different situations, depending on how certain or uncertain the outcome is (and their relation to cause and effect.) Complexity and uncertainty are ever more part of the world and Liz artfully leads us through ways to engage and manage it. If you do not know much about Cynefin, including discussing risk with senior executives, this a golden introduction. Our tour continues with a discussion of Wardley Maps mapping maturity and their use with Cynefin but sadly we didn't have time to deal with a shallow dive into chaos: https://lizkeogh.com/2015/03/09/the-shallow-dive-into-chaos/ There is no silver bullet but Liz is the enemy of inertia, the navigator of uncertainty and generous with her explanations and references to both. A good example to us all.References:Liz Keogh Blog: https://lizkeogh.comTwitter: @lunivoreEscape Velocity: Free Your Company's Future from the Pull of the Past - Geoffery A MooreSimon Wardley (Wardley Mapping) https://twitter.com/swardleyThe Aglie Fluency Model Diana Larsen and James Shawhttps://www.agilefluency.org/assets/downloads/agile-fluency-project-ebook-rtw-1.pdf David Snowden, Cynefin Framework: https://www.youtube.com/watch?v=N7oz366X0-8#agile #waysofworking #agilemethodshttps://agilitybynature.com/contact-us/ Our GDPR privacy policy was updated on August 8, 2022. Visit acast.com/privacy for more information.

Behaviour Driven Development (BDD) is a term that was coined by Dan North in 2006. It came about as a response to a very specific problem – teaching developers how to think about testing their code. It incorporates the ubiquitous language idea from Eric Evan’s book Domain-Driven Design, and this evolved into a technique used by the whole team to collaboratively specify how the finished system should behave. While both approaches focus on collaboration, DDD focuses on a shared model for building software and BDD focusses on specifying the behaviour of the system. So what can we learn from both our techniques? Join us in this session were Seb Rose, Steve Tooke and Matt Wynne will discuss with us how we can improve modelling with BDD. We will bust popular BDD myths and talk about their favourite collaboration techniques.

This month on the Cucumber Podcast Matt Wynne speaks with Andreas Markussen and Sheeraz Iqbal from Nuuday a Danish company which has recently been on a journey of adopting Behaviour-Driven Development. This is a conversation about their story so far and the challenges they've faced.

Guest Bio: Dan North is the originator of Behaviour-Driven Development and Deliberate Discovery.  He has been coaching, coding, and consulting for over 25 years and uses his knowledge to help CIOs, businesses, and software teams to deliver quickly and successfully.  Dan is also a frequent speaker at conferences and has contributed to a number of books, including 97 Things Every Programmer Should Know.   Episode Description: In this episode, Dan shares his excitement on how wide open the field of IT remains, and that it continues to be powered by a strong sense of innovation and creativity. He also talks with Phil about the benefits of choosing your own path, the value of diversity, and the importance of empathy.   Key Takeaways:   (1.22) Phil starts things off asking Dan to tell us more about himself and what he’s working on. Dan talks about how’s been working independently for almost six years now and that one of the downsides of being independent is having to run the actual business as well as do the work and that it takes up time that he would like to spend on book-writing. He adds that he also recently became a father and has less disposable time than ever before “and I couldn’t be happier about it.”   (4.19) Phil then asks Dan to share a unique career tip, to which Dan responds first with the fact that IT as an industry is barely into its second generation and that this can be immensely freeing because it means the industry hasn’t become stuck in a rut of making people do things a certain way. He says that because of this, even people who are new to the business have just as much a chance of making their ideas successful as people who have been in the business for many years.   (8.09) Dan then brings things back around by saying that the best tip he can think to give is for people just starting out in the industry to not “institutionalize themselves” and keep questioning and thinking of better ways to do things because everyone is just “making this up.”   (9.02) Dan continues this line of thought by saying that even if he had been asked as recently as ten years ago, he could not have possibly predicted where we would be today in terms of technology and what would be “hot and exciting.” He also says he can’t wait to see what keyboards finally get replaced with.   (10.41) Phil asks Dan about his worst IT career moment, and Dan tells a story about the second “real” job he ever had, where he was the senior software engineer for a database marketing business. He describes that there was one single database that essentially did everything for the company and that he, by typing something in the wrong terminal, accidentally shut down, along with the entire server. Dan says that rather than punish or fire him, that his boss instead told him that he was going to learn about database restores, and they manually restored the database all night.   (15.59) Phil moves on to asking about career successes, and Dan replies that he actually has a hard time thinking of what’s been the highlight of his career because he’s still learning and growing and that he has not had a very straightforward career path. Dan continues that rather he’s always just gone after opportunities as they appeared or based on what interested him and that even things he’s proud of, such as the first time he was a keynote speaker at a conference, happened essentially by accident. He emphasizes not getting too hung up on having a rigid career plan, as it can lead to you missing out on interesting experiences and opportunities.   (19.04) When Phil asks what excites Dan most about the future of IT, he reiterates that what excites him the most is that he has no idea what the future of IT will look like. Apart from that, he says that the strong shift towards more diversity in the field of IT excites him very much because it means opening up a much larger talent pool of different viewpoints, life experiences, and ways of thinking.   (22.41) On the topic of the best career advice that he’d ever received, Dan responds that it was actually advice from a friend in the context of relationship problems he was having and that it was to “never settle for second best.” Dan adds that it has translated into every part of his life, such as looking at jobs and asking himself if he’s just taking a job because it’s there and settling.   (24.35) On that note, Phil asks Dan about his current career objectives, to which Dan says that mostly he’s just trying to find interesting people and interesting challenges before adding that he’s tinkering with an idea for finding a better way to locate people for jobs that are good at working on teams in a way that gets people excited and motivated and can grow a team. Phil notes that people with these qualities are hard to find but easy to spot.   (28.16) Upon being asked about the non-technical skill that he has found the most useful, Dan mentions listening as a “powerful non-technical skill,” before adding that he also thinks that sharing information and empathy are both incredibly important as well.    (31.04) Lastly, Phil asks Dan if he has any final words of advice for someone starting a career in IT. Dan advises that someone should always do the best they can at whatever job they happen to be doing. He says that even if it feels like a pointless task if you always do your best someone is going to recognize that.   Best Moments:   (6.51) Dan: “So my big unique career tip would be to just be aware that we’re making this up. This isn’t just Imposter Syndrome...it’s literally, the things we’re doing, no one knew about earlier.”   (8.09) Dan: “Don’t institutionalize yourself, we are making this up.”   (8.12) Phil: “I think any new career or technology is gonna go through those learning pains as well. If nobody’s been there and done it before, it’s all new, by definition.”   (18.03) Dan: “I’d say the only deliberate career move I’ve made was going independent just five and a half years ago...and I had no idea what I was gonna do or where it was gonna go...and I’m still not entirely sure what I want to be when I grow up. But I’m having some adventures, and I’m working with some really interesting organizations.”   (30.32) Dan: “As a developer, understanding who you’re building software for is massive. As a manager, understanding that if you have a struggling team, you don’t have a struggling team you have a system of work that presents as a struggling team, so you need to go fix the system of work. It’s understanding the interconnectedness of things.”   (31.04) Dan: “Whatever you’re doing, do it the best that you can, even if it’s a thing that you think sucks, even if you don’t see the point of it.”    Contact Dan North LinkedIn: https://www.linkedin.com/in/dannorth/ Twitter: https://twitter.com/tastapod @tastapod Website: https://dannorth.net/ Contributor to Book: https://www.amazon.com/Things-Every-Programmer-Should-Know/dp/0596809484    

A conversation with Agile coach Dan North about his pioneering work with Behaviour Driven Development, the Agile certification racket and how Agile breaks everything.For more on Dan North's work, head to www.dannorth.net.Being Human is a FirstHuman production. For more on FirstHuman's coaching and leadership programmes, head to http://www.firsthuman.com.

A conversation with Agile coach Dan North about his pioneering work with Behaviour Driven Development, the Agile certification racket and how Agile breaks everything.For more on Dan North's work, head to www.dannorth.net.Being Human is a FirstHuman production. For more on FirstHuman's coaching and leadership programmes, head to http://www.firsthuman.com.

A conversation with Agile coach Dan North about his pioneering work with Behaviour Driven Development, the Agile certification racket and how Agile breaks everything.For more on Dan North's work, head to www.dannorth.net.Being Human is a FirstHuman production. For more on FirstHuman's coaching and leadership programmes, head to http://www.firsthuman.com.

CukenFest London is coming to town over June 21st-25th. Three events for the Cucumber, BDD, and Agile communities. Learn more about the events on our website - http://cukenfest.cucumber.io/ This month on the Cucumber podcast, Matt Wynne speaks to Simon Powers the founder of Adventures with Agile about Behaviour-Driven Development in banking. Simon was approached by the global investment bank BNP Paribas to review several product teams and to find out why the teams could not complete stories at the end of each sprint and why there was so many defects coming into the sprint. In just 9 months, the defect rate decreased from 34% to 4% and they avoided a very costly rewrite. Listen to this podcast to hear how they did it and the lessons learned along the way. Read the short case study on the [Adventures with Agile website](https://www.adventureswithagile.com/2015/08/27/a-case-study-for-bdd-in-improving-throughput-and-collaboration/) Cucumber and Adventures with Agile are teaming up to run BDD Kickstart, London. A two-day public training course for people who want to learn fundamentals of BDD and Cucumber. Aslak Hellesoy - the creator of Cucumber and author of The Cucumber Book - will teach this course. [Learn more][https://cucumber.io/events/bdd-kickstart-london)

Shane Hastie spoke to Chris Matts “The IT Risk Manager”, one of the original thinkers behind Real Options, Feature Injection and Behaviour Driven Development, about BDD, Real Options, Risk Management and the Impact of Culture for Effective Outcomes. Why listen to this podcast: - Real Options is about translating the ideas from financial risk management into IT projects - Understanding that things go wrong and that what is thought of as the last responsible moment is often actually too late and is in fact an irresponsible moment - Most of the challenges to agile adoption are far above the level of the delivery team - Introducing a simple governance framework which supports an agile culture - The difference between the community of needs and the community of solutions, and the need for both More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2pes3jD 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 Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pes3jD

Long before Behaviour-Driven Development was a term, John Smart was a proponent of bringing business and tech teams together. It was working for a French insurance company in the 90s, with complex (and peculiar) business rules, where the journey started: “This was a car insurance company so you had to tell them where you lived, what sort of car you had, what colour it was, what sort of dog you had...everything. The customer/product owner had these excel spreadsheets that he was using by himself to check the algorithms on the mainframe that we were supposed to be reproducing. So I said, maybe that could be useful - we can use those to drive our tests. What we ended up with was a set of unit tests being driven by an Excel spreadsheet...Ever since then, I’ve been looking for ways to write tests that express things at the business level. So when I came across BDD it all fell into place. “ This week on the Cucumber Podcast, Matt Wynne, Aslak Hellesøy and Steve Tooke talk with John Smart about BDD, his upcoming CukeUp! workshop, and how Serenity can help your team write higher quality automated tests. John Smart will be delivering a workshop at CukeUp! London on April 14th - skillsmatter.com/conferences/7606…eup-2016#program John was a speaker at CukeUp! in Sydney last November. His talk can be found here - cucumber.io/blog/2016/01/11/cuk…5-videos#john-smart You can find out more about Serenity on his website - www.thucydides.info/#/ Other speaking engagements - DevWeek London - devweek.com/speakers#john-smart - Gee Con - 2016.geecon.org/speakers/info.html?id=87 - London Tester Gathering - skillsmatter.com/conferences/7219…g-workshops-2016

Author: Konstantin Kudryashov Read By: Alfred Nutile Original Source: http://stakeholderwhisperer.com/posts/2014/10/introducing-modelling-by-example "For the last year I have been experimenting with the new approach to a Behaviour-Driven Development, which could be summarised as "Ubiquitous Language is a thing again". The core premise of this approach is that if you take Ubiquitous Language seriously and push for it in your scenarios, you open the door to doing a Domain-Driven Design while you're doing Behaviour-Driven Development's red-green-refactor cycle. By embedding Ubiquitous Language in your scenarios, your scenarios naturally become your domain model, which you can use to develop the most important part of your application - a core domain."

Testing Acceptance and Behaviour Driven Development (mp3), recorded at CITCON ANZ 2010 at Fronde in Wellington, New Zealand.Theme music is Fireworks by Knoxville, used under license of Creative Commons.