Podcasts about test driven development tdd

This episode of Remote Ruby starts with Andrew and Chris discussing how busy they are this month and how they're managing new feature releases, travel, and bulk recording episodes. They continue answering listener questions from Episode 300, covering key improvements they wish to see in Rails, best practices for hybrid remote work, and methods to inspire teams about Object-Oriented Programming (OOP) and Test-Driven Development (TDD). They share advice on attending Ruby conferences, including how to justify the cost to employers and the immense networking benefits. Lastly, they tackle how freshers can secure remote Ruby jobs and provide tips on writing blog posts to enhance learning and visibility in the developer community. Hit the download button now! LinksJudoscale- Remote Ruby listener gift99 Bottle of OOP by Sandi MetzPractical Object-Oriented Design (POODR) by Sandi Metzconventional: commentsPodiaRemote Ruby Podcast-Episode 293: Jason's Farewell-So Long, and Thanks for All the BETs!HatchboxKamalMCP.RBJosh Branchaud's TIL (Today I Learned) repo Chris Oliver X/Twitter Andrew Mason X/Twitter Jason Charnes X/Twitter

In this podcast episode, Steven R. Baker dives into test doubles like mocks and stubs, discussing their essential role in robust code development and challenging traditional testing practices. The conversation covers the nuances of Test-Driven Development (TDD), including writing failing tests first for better code clarity and test coverage, and explores RSpec's influence on TDD. Additionally, Steven examines Ruby's adaptability and the integration of AI in programming, providing listeners with actionable strategies for more maintainable codebases and a balanced view on AI's evolving role in software development.

In this Mob Mentality Show episode, we dive into the journey of Jeff “Cheezy” Morgan, a coach in Continuous Delivery (CD) and lean thinking. Known for his role in advocating for CD within companies, Jeff shares how his experiences with software development and his recent shift into the café business have shaped his philosophy on people and just-in-time. This discussion explores how Jeff's approach to Agile and CD evolved, his journey into Extreme Programming (XP), and how mob programming impacted his perspective on teamwork and Continuous Integration (CI).  **Jeff's Agile and CD Journey** We start with Jeff's introduction to Agile, discussing the early days of his career when dev practices didn't include CD and the impact of adopting CD in high-stakes projects like Y2K. Jeff describes how learning from Thoughtworks influenced his views on XP and CD, and how he became an advocate, eventually taking CD to different organizations. He also shares what it was like discussing with Woody Zuill and Llewellyn Falco and reflects on the transformative role mob programming has played in his career. **From Pairing to Mobbing**   For Jeff, mob programming was not initially appealing, but over time it became his preferred approach for helping teams. We explore how mobbing enhances CI, tightens communication, and fosters collective learning. Jeff explains how mobbing enables "just-in-time" discussions that align teams on what to build and how it allows real-time feedback on other team members' learning. Jeff also examines the transition from pairing to mobbing, the challenges of mob programming with CI/CD, and why mobbing helps him “get the whole system in the room” for tackling complex problems. **Quality Without QA?**   We dive into the controversial idea of achieving high quality without traditional Quality Assurance (QA). Jeff opens up about years spent wrestling with the role of QA in Agile/CD environments and shares experiments with “test-infected” developers—who took full ownership of quality. He reflects on the pitfalls of relying on “heavyweight” traditional QA processes and automated tests, which often create lean waste, add handoffs, and introduce brittle, flakey tests. Jeff and hosts Austin and Chris discuss whether “shift left” is merely a shift away from QA, the Deming Red Bead experiment's relevance, and whether there's a happy journey for QA professionals on CD teams. **Applying Lean to Cafés**   Outside the tech world, Jeff has found a second passion—running cafés. We discuss how owning two cafés influenced Jeff's perspective on Lean thinking and Agile principles. From supply chain issues during COVID to needing backup suppliers, Jeff discusses if “just-in-time” challenges in the café world mirror software development. He shares valuable insights about hiring, managing consistent delivery, and applying Lean principles to run a resilient business. Additionally, Jeff and Chris exchange stories on chip shortages and if Lean can help address real-world supply chain issues. **More from Jeff**   Finally, we tackle some big questions: What does DevOps mean in today's Agile world? Should “DevOps” be responsible for shielding organizations from developers? How does Test-Driven Development (TDD) factor into DevOps scripts, and can mobbing help break down silos that traditionally separated devs, ops, and QA? Join us for this wide-ranging conversation with Jeff “Cheezy” Morgan to uncover actionable insights for anyone involved in Agile, CD, DevOps, or Lean. Whether you're in software, QA, or running a small business, this episode is packed with valuable takeaways on quality, learning, and resilience.  Video and Show Notes: https://youtu.be/OJ5d6qLIQRY   

In this exciting episode of the Mob Mentality Show, we are joined by Kyle Griffin Aretae to dive deep into the nuances of Test-Driven Development (TDD) and the crucial concept of "Goal-Centricity" in Agile practices. Kyle breaks down why TDD is so much more than just "test first" and challenges common misconceptions about this widely used development practice. If you're a software developer, Agile enthusiast, or just someone looking to refine your team's development processes, this episode is packed with insights you won't want to miss. We explore why treating TDD as merely writing tests first misses the larger picture and how adopting a broader, more progressive approach can help your team build better, more maintainable software. Kyle shares his thoughts on the primary value proposition of TDD, focusing on **fast feedback loops** and the **refactor step** at least every 5 minutes. He explains how smaller, healthier TDD cycles allow developers to stay nimble and avoid the trap of feedback loops that last 30 minutes or more. Thus, when fast feedback loops with constant refactoring are in place as the foundation, then the "test first" aspect of TDD really shines.  Kyle also sheds light on common pitfalls, such as the misunderstanding of what it means to "do TDD" when developers claim they have 8 unit tests on 50,000 lines of code. We discusses the difference between **Cargo Cult XP (Extreme Programming)** and the real deal, as well as the critical role of **decoupling code** so tests can run in 5 seconds or less.  A key takeaway from this episode is the impact of **social programming**, TDD, and **CI/CD (Continuous Integration/Continuous Delivery) pipelines**. We explain the importance of the "Pipeline First" principle when writing new code. We then dive into Kyle's most controversial take on TDD: the idea that creating a **mini-plan** (a rough roadmap of what to do next) before writing tests might actually be more beneficial than strictly adhering to "test first." This, Kyle argues, leads to more robust code when integrated into strong social programming practices. We also touch on the application of **Maslow's Hierarchy of Needs** to TDD and the importance of satisfying basic development needs (like fast feedback and clean code) before tackling more complex issues. The episode continues with a discussion on the intersection of **Goal-Centricity** and Agile. Kyle questions whether Agile methods are effective without first agreeing on a clear goal. We explore scenarios where goals are unclear or where methods are imposed without understanding the desired outcomes. Kyle shares a fascinating example of a code freeze during "Black Friday" and the unintended consequences of such decisions. We also reference a powerful quote by **Deming**, "A goal without method is cruel," explaining how the opposite can be just as problematic. Throughout the conversation, we dive into the importance of aligning goals between management and development teams, avoiding the common trap of blindly delivering fixed requirements for bonuses, and how real Agile success comes from alignment on solving customer problems, not just ticking off tasks. Kyle emphasizes the need to start with a clear understanding of what you're trying to achieve before applying any method, whether it's Scrum or TDD. Don't miss out on this thought-provoking episode filled with actionable insights on TDD, Agile, and effective software development. Subscribe today and tune in to hear Kyle Griffin Aretae's unique take on how to elevate your development practices! Video and Show Notes: https://youtu.be/S7K8lSibmII  

It's back to school, everyone! Dive into a transformative journey of education with Matthew Philip, an experienced Organizational Refactorer and educator, as he shares his innovative approach to integrating XP (Extreme Programming) and Agile methodologies into the classroom. In this episode of the Mob Mentality Show, we explore how Matthew's dynamic teaching methods are applied to software engineering education, fostering an environment where trust, mastery, and psychological safety are paramount. **XP and Agile in the Classroom** Matthew Philip's unique perspective as both an educator and coach provides a compelling narrative on how XP and Agile principles can be implemented in higher education. From his history of teaching Agile in orgs and universities to leading hands-on learning experiences that go beyond traditional lectures, Matthew's methods challenge the conventional constraints of the classroom. Discover how Matthew creates a WAR room environment in the classroom, fostering high energy and positivity to encourage active participation. Learn about the use of information radiators, pairing, and mob programming to ensure students not only grasp theoretical concepts but also excel in real-world applications. Matthew also delves into the challenges of teaching Agile content as part of a master's program in software engineering, where students are exposed to the intricacies of refactoring to patterns and leading through facilitation. In this episode, we discuss the critical differences between being a crafter versus just a coder, and how Matthew helps students navigate the transition from the academic world to the corporate environment. We explore the importance of understanding short-term school code versus long-term maintainability, and how working with real customers in a classroom setting can profoundly impact students' learning experiences and feedback loops. **Mastery-Based Learning and Psychological Safety** Matthew is a strong advocate for mastery-based learning, where the focus shifts from simply passing quizzes to deeply understanding and applying knowledge. We discuss how students can assess their own understanding, whether through techniques like Test-Driven Development (TDD) or experiencing the consequences of poor practices. Matthew emphasizes the significance of psychological safety in the classroom, where students learn how to fail safely and collaborate effectively. Explore how the pressure of pacing in large classrooms can conflict with mastery learning, and how assessment strategies can be adapted to ensure that learning sticks and isn't lost over time. Matthew shares insights on fostering peer assessments and creating systems where even when students "game" the system, true mastery is still achieved. **The Role of AI and Future of Education** In a rapidly evolving educational landscape, Matthew addresses the impact of generative AI in the classroom. How can AI be leveraged to enhance learning, and what are the risks of its misuse? We discuss the importance of correct prompting, the authenticity of AI-generated content, and whether mob programming could be the solution to these challenges—while also questioning whether this approach could disrupt current educational and industry standards due to teacher-to-student ratios. **Psychological Safety and Building Trust** Finally, we delve into the role of psychological safety in the classroom, exploring how activities like group juggling can teach students to fail and learn together. Matthew shares strategies for establishing trust and the correlation between high energy, positivity, and psychological safety. We also consider whether in-person interactions are essential for fostering trust, or if remote environments can replicate these conditions. Don't miss this episode as we uncover the future of education, one where trust, mastery, and psychological safety take center stage. To stay updated on this and other insightful episodes, subscribe to the Mob Mentality Show on your favorite platform. Video and show Notes: https://youtu.be/IkqRI2GQ4MY  

O Let's Data é o seu podcast sobre dados e carreira!Neste episódio falamos sobre o conceito de Test Driven Development (TDD) que é uma metodologia em que a programação é desde o início voltada para testes.Adaptando a metodologia de desenvolvimento voltada para os testes, damos alguns exemplos de como isso pode ser aplicado para dados. Falamos também sobre alguns tipos de testes que são usados, como são implementados, além da importância de ter essa metodologia implementada desde o início de um projeto.

In this special crossover episode recorded live from RailsConf 2024 in Detroit, join us for a unique gathering of prominent Ruby podcasters. Drew teams up with Elise from the 'Ruby on Rails' podcast, Jason from 'Code with Jason,' Joël from 'The Bike Shed,' and Julie from 'Ruby for All' The group discusses their experiences at RailsConf, including workshops, talks about Test Driven Development (TDD), and building dynamic applications with Turbo. They delve into the implications of RailsConf being discontinued after 2025, the thriving local Ruby conference scene, and share candid moments about their interactions with the community. Additionally, they touch upon diverse topics such as Detroit-style pizza, hot dog eating capacities, and food opinions, blending technical insights with light-hearted banter. The episode concludes with gratitude for the well-coordinated event and excitement for future Ruby gatherings. Enjoy!Panelists:Julie J.Elise ShafferJason SwettDrew BraggJoël QuennevilleLinks:Julie J. TwitterJulie J. WebsiteRuby for All PodcastJason Swett TwitterCode with Jason WebsiteJoël Quenneville TwitterJoël Quenneville WebsiteThe Bike Shed PodcastElise Shaffer WebsiteThe Ruby on Rails PodcastRailsConf 2024Send us some love.HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the Show.Ready to start your own podcast?This show is hosted on Buzzsprout and it's awesome, not to mention a Ruby on Rails application. Let Buzzsprout know we sent you and you'll get a $20 Amazon gift card if you sign up for a paid plan, and it helps support our show.

In this special crossover episode recorded live from RailsConf 2024 in Detroit, join us for a unique gathering of prominent Ruby podcasters. Julie teams up with Elise from the 'Ruby on Rails' podcast, Jason from 'Code with Jason,' Joël from 'The Bike Shed,' and Drew from 'Code and the Coding Coders Who Code It.' The group discusses their experiences at RailsConf, including workshops, talks about Test Driven Development (TDD), and building dynamic applications with Turbo. They delve into the implications of RailsConf being discontinued after 2025, the thriving local Ruby conference scene, and share candid moments about their interactions with the community. Additionally, they touch upon diverse topics such as Detroit-style pizza, hot dog eating capacities, and food opinions, blending technical insights with light-hearted banter. The episode concludes with gratitude for the well-coordinated event and excitement for future Ruby gatherings. Enjoy![00:00:30] Live from RailsConf Detroit[00:01:04] Meet the Hosts[00:01:38] Conference Highlights and Workshops[00:07:21] The Future of RailsConf[00:12:10] Community Interactions and Podcasting[00:14:21] Exploring Detroit[00:17:30] Exploring Unique Pizza Toppings[00:18:02] Pittsburgh's Pierogi Pizza[00:18:20] The Versatility of Pizza[00:19:17] Controversial Pizza Opinions[00:20:43] Coney Island Hot Dogs in Detroit[00:21:19] Hot Dog Eating Contest[00:21:39] Food Preferences and Eating Habits[00:26:06] Snail Mail Programming Newsletter[00:27:24] Conference Highlights and Expectations[00:30:50] Wrapping Up the PodcastPanelists:Julie J.Elise ShafferJason SwettDrew BraggJoël QuennevilleSponsors:HoneybadgerGoRailsLinks:Julie J. TwitterJulie J. WebsiteDrew Bragg TwitterCode and the Coding Coders who Code it Podcast with Drew BraggJason Swett TwitterCode with Jason WebsiteJoël Quenneville TwitterJoël Quenneville WebsiteThe Bike Shed PodcastElise Shaffer WebsiteThe Ruby on Rails Podcast RailsConf 2024 (00:30) - Live from RailsConf Detroit (01:04) - Meet the Hosts (01:38) - Conference Highlights and Workshops (07:21) - The Future of RailsConf (12:10) - Community Interactions and Podcasting (14:21) - Exploring Detroit (17:30) - Exploring Unique Pizza Toppings (18:02) - Pittsburgh's Pierogi Pizza (18:20) - The Versatility of Pizza (19:17) - Controversial Pizza Opinions (20:43) - Coney Island Hot Dogs in Detroit (21:19) - Hot Dog Eating Contest (21:39) - Food Preferences and Eating Habits (26:06) - Snail Mail Programming Newsletter (27:24) - Conference Highlights and Expectations (30:50) - Wrapping Up the Podcast

Welcome back to another episode of Building Better Developers. Today, we're tackling an issue that every developer faces at some point: panic during software delivery. Whether it's a critical bug or a new feature that isn't functioning as expected, panic can strike anytime your software fails in the hands of a user. Rob and Michael cover handling software delivery panic with practical tips and real-life examples. Listen to the Podcast on Handling Software Delivery Panic The Inevitable Bug: Why Panic Happens Delivering software is a delicate process. Even when you've thoroughly tested your code and believe it to be bulletproof, something can always go wrong. Often, the panic ensues because: Unexpected User Behavior: Users may interact with the software in ways you didn't anticipate. This is particularly common in beta tests or early releases where feedback is crucial. Overlooked Bugs: Some users have a knack for breaking things. These users often find bugs that slipped through your QA processes. Critical Stakeholders: When a manager, CEO, or client encounters a problem, the stakes feel much higher. Their frustration can quickly escalate to panic. Real-Life Panic: A Case Study on Handling Software Delivery Panic Recently, Rob faced this scenario with a technically knowledgeable customer. Despite understanding the development process, the customer encountered a show-stopping bug in an alpha version. Their immediate reaction was that the project was nowhere near completion, creating a sense of panic. During our call, he expressed concerns that none of the features seemed to work. He acknowledged that bugs and design flaws were expected at this stage, but the issue was so severe that it led to a dramatic loss of confidence in the project. Handling Software Delivery Panic Step 1: Stay Calm and Analyze The first and most crucial step when faced with panic is to stay calm. Take a deep breath and focus on understanding the situation: Reproduce the Issue: Identify the user's steps to encounter the bug. Sometimes, it's as simple as a permission issue or an unanticipated input. Prioritize Fixes: Address the most critical issues first, especially those that block user progress. Step 2: Effective Communication Reassure the stakeholders that you're on top of the situation: Acknowledge the Problem: Validate their concerns and show you understand the impact. Outline the Next Steps: Explain how you plan to fix the issue and provide a realistic timeline. Step 3: Learn and Improve Use this experience to strengthen your development and testing processes: Enhance Testing: Incorporate the steps that led to the bug into your testing scenarios. Automated tests can help catch these issues earlier. Add Logging: Improve logging to gather more information if a similar problem arises in the future. Real-Life Tips from Experience Michael shares an insightful story about a shared work experience. Despite rigorous testing, their boss would find bugs within minutes of a release. This constant scrutiny drove home the importance of thorough testing and the psychological pressure of delivering seemingly flawless code. One key takeaway from Michael's story is the value of Test-Driven Development (TDD). By writing tests before the actual code, you ensure that each function meets the specified requirements. This approach not only catches potential issues early but also clarifies the expected behavior for each part of your application. Practical Advice for Developers Before starting on a new feature or bug fix, consider the following: Clarify Requirements: Ensure you have detailed requirements, including user input constraints and expected outputs. Define Acceptance Criteria: Clearly outline what constitutes a successful implementation. Implement Robust Logging: Log critical operations to simplify debugging and provide insights into any issues that arise. Using Static Code Analysis Tools To Handling Software Delivery Panic SonarQube SonarQube Is a code quality assurance tool that performs in-depth code analysis and generates an analysis report to ensure code reliability. Language Support: Java, JavaScript, C#, PHP, Python, C++, and more. Features: Provides comprehensive code quality and security analysis, integrates with CI/CD pipelines, and offers detailed reports. Strengths: Strong community support, extensive plugin ecosystem, and good integration with various development tools. ESLint ESLint statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your continuous integration pipeline. Language Support: JavaScript, TypeScript. Features: Identifies and reports on patterns in JavaScript, customizable rules, and integration with most text editors and build systems. Strengths: Highly customizable, large number of plugins, and widely used in the JavaScript community. PMD PMD is an extensible multilanguage static code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, etc. Language Support: Java, JavaScript, Salesforce Apex, PLSQL, XML, XSL. Features: Detects common coding issues like bugs, unused variables, and performance bottlenecks. Strengths: Simple rule configuration, supports multiple languages, and can be integrated into build tools like Maven and Gradle. PyLint Pylint is a static code analyser for Python 2 or 3. The latest version supports Python 3.8.0 and above. Pylint analyses your code without actually running it. It checks for errors, enforces a coding standard, looks for code smells, and can make suggestions about how the code could be refactored. Language Support: Python. Features: Checks for coding standards, errors, and code smells, provides suggestions for code improvements. Strengths: Highly configurable, integrates well with IDEs and CI/CD pipelines, and widely used in the Python community. Final Thoughts on Handling Software Delivery Panic Panic during software delivery is unavoidable, but it's manageable. By staying calm, communicating effectively, and learning from each incident, you can turn these challenging moments into opportunities for improvement. Remember, every bug is a lesson in disguise, pushing you toward becoming a better developer. That's it for today's episode. We hope these insights help you handle panic more effectively and continue building better software. Until next time, keep calm and code on! Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Code Refactoring: Maintaining Clean, Efficient Code Deciphering Code Chaos: Strategies for Writing Maintainable Code Test-Driven Development – A Better Object Oriented Design Approach Behind the Scenes Podcast Video

BONUS: The Art of Slicing Work with Anton Skornyakov This episode features Anton Skornyakov, an expert in Agile methodologies and the author of "The Art of Slicing Work: How to Navigate Unpredictable Projects." Let's unpack the concept of slicing work and explore how it can revolutionize productivity and project management. Inspiration Behind The Book "Focusing on 'what's the result we want from this discussion' shifts our mindset towards more practical, outcome-oriented conversations." Anton shares what drove him to write his book. In his coaching practice, he noticed that many organizational discussions were mired in theory rather than focusing on actionable outcomes. By centering the conversation on "the next step" and the desired results for the upcoming two weeks, teams can move from abstract planning to concrete, actionable steps. Understanding Slicing Work "Think of work like a large dinner; slicing it into dishes rather than tasks offers flexibility and maintains the connection between different work elements." In his book, Anton introduces the concept of Slicing Work using the metaphor of preparing a large dinner. He explains that traditional task division (horizontal slicing) often leads to a loss of flexibility and a disconnection between different parts of a project. Instead, he advocates for vertical slicing, where each slice represents a complete unit of value, enhancing coherence and team productivity. Common Barriers to Slicing Work "Old habits and upfront software design practices prevent effective work slicing; adopting Test-Driven Development (TDD) can help overcome these barriers." Anton discusses the habitual and educational barriers that prevent effective slicing of work. Many professionals are trained to focus on their specific expertise and to plan extensively before starting actual development, practices which can impede the flexible and iterative nature of Agile methodologies. In this segment, we refer to Extreme Programming and the pattern of the tracer bullet. The Slicing Work Mindset "Empowering teams to feel they can reshape their work structure is crucial for successful implementation of work slicing techniques." Implementing work slicing techniques can be straightforward technically, but the real challenge often lies in changing the organizational mindset. Anton points out that teams may understand the concept intellectually but often struggle with feeling empowered to change existing processes. Addressing Leadership Skepticism "Instead of promoting slicing, I discuss potential risks with leaders to help them see the value in breaking down projects to manage risks effectively." When faced with leadership skepticism, Anton shifts the conversation from slicing work per se to managing project risks. By identifying what could go wrong and finding ways to address these risks incrementally, leaders can see the practical benefits of adopting slicing work techniques. The Future of Work with Full Adoption "By turning Agile up to 11, micromanagement becomes obsolete, and teams are empowered to focus on transparent, result-driven discussions." Anton envisions a future where complete adoption of slicing work principles leads to a significant transformation in how teams and stakeholders interact. With a focus on frequent, tangible results and pragmatic discussions, organizations can achieve greater transparency and reduce the need for micromanagement. About Anton Skornyakov Anton Skornyakov is the co-founder and managing director of Agile.Coach. He has coached nearly a hundred organizations and thousands of people in the art of slicing work. His insights are distilled in his latest book, "The Art of Slicing Work," which encapsulates a wealth of stories, lessons, and principles from his extensive experience. For more information, visit slicingwork.com. You can link with Anton Skornyakov on LinkedIn.

Today we are talking about Test Driven Development, Why it's important, and How it improves development with guest Alexey Korepov. We'll also cover Test Helpers as our module of the week. For show notes visit: www.talkingDrupal.com/446 Topics What does the term Test Driven Development (TDD) mean Does Drupal make use of TDD What makes TDD different from other methods of Development Do you have to change your way of thinking What are some good resources to learn TDD Do you have any pointers for teams looking to get started Are certain kinds of projects better suited to TDD How have dev teams adapted to TDD Any advice on environment setup Any special tools Resources Open telemetry QA Engineer Kent Beck Test Driven Development: By Example Needs tests tag Local unit tests PHPUnit Guests Alexey Korepov - korepov.pro Murz Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Martin Anderson-Clutz - mandclu Matt Glaman - mglaman.dev mglaman MOTW Correspondent Martin Anderson-Clutz - mandclu Brief description: Have you ever wanted an API that could dramatically simplify the process of writing Drupal unit tests? There's a module for that. Module name/project name: Test Helpers Brief history How old: created in Sep 2022 by today's guest, Alexey Korepov Versions available: 1.3.0 compatible with versions of Drupal 9.4 or newer, right up to Drupal 11 Maintainership Actively maintained, latest release less than 3 months ago Security coverage Test coverage, would be ironic if it didn't API Documentation is available, linked from the project page Number of open issues: 2 open issues, which are actually feature requests Usage stats: 5 sites officially, but modules or sites can leverage Test Helpers without enabling it, and this usage is recommended, so the number is actually higher Module features and usage Provides a new container that automated tests can leverage to perform common tasks with much less code. For example, you can create a user or a node with a single line of code You can also mock more complex operations like an entityQuery or loadMultiple call, again with a single line of code Traditionally, writing unit tests is more complicated because by design they run without fully bootstrapping Drupal That means that your test needs to mock functions or services in the code you're testing which can result in units tests being much longer than the code they're testing Test Helpers also allows your tests to leverage existing mocks and stubs for popular services The project page also links to the recording and slides for a talk Alexey gave about Test Helpers at DrupalCon Pittsburgh last year, if you want to do a deeper dive

Querida tecnología, hoy hablamos de TDD, la metodología que cambia el paradigma del desarrollo de software donde las pruebas unitarias impulsan el proceso de la implementación de la lógica. ¡Dale al play y descubre sus ventajas! Música: ⁠Aliaksei Yuknhevich - Background Ukulele⁠⁠ ⁠⁠Makesound - Ambient Motivational Inspirational⁠⁠

We chat with Trisha Gee about Test Driven Development (TDD), flaky tests, ops & observability for builds, and developer productivity. Mentioned TDD Article: The beautiful theory of TDD and the reality check of practice Discuss this episode: ⁠discord.gg/XVKD2uPKyF

Join us for an insightful conversation with Philip Markgraf on how Mobbing serves as the keystone of the third generation of XP, pushing the boundaries of innovation, evolution, and continuous improvement. In this episode, we explore: 1. The Evolution of XP Practices in Phil's Mobs Dive into the nuances of "full mob" adoption and its implications for team dynamics. Discover simple definitions that unveil the deeper richness of mobbing. Is mobbing synonymous with "all the good things," or, is it simply "all the brilliant minds working on the same thing, at the same time, in the same space, on the same computer"? Explore the importance of a good player/coach in fostering effective mobbing. Contrast building a mob team from scratch with introducing mob Test-Driven Development (TDD) to existing teams. Is good mobbing the cornerstone to all else? Or, is it TDD? Or, is it The Virtuous Loop? 2. Mobbing in Safety-Critical and High-Reliability Software Understand the rationale behind TDD mobbing in safety-critical systems. Delve into the challenges of achieving zero bugs in medical and safety-critical environments. Uncover ways to address the issue of flakey end-to-end tests in critical systems. 3. Lightweight Methodologies for Regulated Industries Follow Phil's journey from embedded systems to mob programming. Gain insights into applying XP in Embedded and IoT development. Explore mobbing experiments in electrical engineering, mechanical engineering, firmware, and software. 4. Solo Programming After 20 Years of Mobbing Navigate the challenges of solo programming after years of pairing and mobbing. Tackle loneliness and loss of motivation in the absence of collaborative programming. Discover strategies for playing the Mob RPG alone and staying motivated. Tune in for a captivating discussion that transcends traditional programming methodologies! Video and Show Notes: https://youtu.be/Y4aHoiKh2XA  

Dive into the world of zero bugs and lean mobbing with David Batten on this episode of Mob Mentality Show. Discover the distinction between the scary and healthy versions of zero bugs, and explore how David and his teams achieved a bug-free environment. Uncover insights on when to shift focus away from zero bugs, anti-patterns to avoid, and the art of baking quality into your code.  Explore the synergy of Lean principles, Continuous Delivery (CD), and Test Driven Development (TDD) as David shares how they got to zero bugs as a natural side effect. Learn about the application of the prime directive to foster continuous improvement and the joy of being in a bug-free system.  Explore the facet of Lean where we draw systems and seek ways to shorten feedback loops. Gain insights into the business perspective on Lean and the power of tiny commits. Understand the role of Lean in risk conversion, frequency, and Domain Driven Design (DDD) for organizational simplicity. Join us in exploring the art of mobbing as David recounts his first mobbing experience to meet a deadline and shares his 9 years of mobbing wisdom. Learn how having the entire system in the room ensures that when it's done, it's truly done. David also discusses the impact of mobbing on CD, the benefits of bringing the best of everyone into the code, and a sneak peek into the April 2024 Teaming Conference. If you're passionate about #mobprogramming, #bugszero, #continuousdelivery, #tdd, #leanthinking, #xp, this episode is a must-listen. Elevate your coding mindset and join the conversation on achieving zero bugs naturally through lean mobbing! Video and Show Notes: https://youtu.be/8-EL9x89Ag0 

In this conversation live from RubyConf San Diego, Andrew and Julie sit down with Elise Shaffer, host of The Ruby on Rails Podcast. They kick things off with sharing conference experiences, the joy of reconnecting with friends, and the unique energy the in-person events bring. The discussion shifts to the concept and practice of Test Driven Development (TDD), its benefits, and how it aids in problem-solving during coding.  An interesting point is discussed about whether tests or code should be written first, and whether it's okay to write tests after the code.  They also dive into the handling of tests on legacy codes within Rails. The conversation wraps up with gratitude to the organizers, speakers, volunteers, and attendees at RubyConf. Press download now to hear more! [00:00:24] Elise shares her conference experience mentioning enjoying the sessions and seeing friends from previous conferences, and Julie and Andrew share their joy of being in the company of friends, the conference atmosphere, and food.  [00:01:39] Elise shares the number of Ruby and Rails conferences she's attended and her most memorable one which was Steel City Ruby, highlighting the value of smaller conferences and tight-knit communities. [00:02:45] They discuss the difference between in-person and online conferences, agreeing that in-person events offer more energy and interaction. [00:03:50] The conversation shifts to memorable conferences as Andrew reminisces about his first conference experience at RailsConf in Pittsburgh. Julie talks about her first conference, RailsConf 2022 in Portland, where she met Elise and Andrew and where Ruby for All was conceived.[00:06:12] Andrew asks Julie about her rise in popularity withing a year, moving from a newcomer toa recognized member of the community. The group jokes about autographs and fame within the Ruby community. Elise shares her role in the community, especially with the podcast she hosts. [00:09:33] Elise and Andrew discuss the technical aspects of testing and continuous integration within software development. She explains her background in Ruby and Rails, where she focused on testing and its challenges in larger applications, and she discusses strategies for testing and the importance of testing not every permutation but preventing major issues, [00:12:46] Julie asks Elise to explain parallelized testing.  Elise details using CircleCl or other runners to break up many tests across multiple workers to speed up the process.[00:13:56] Elise explains what Test Driven Development (TDD) means to her, and Julie asks whether TDD is always applicable, like when fixing a bug rather than creating a new feature. [00:15:30] Elise wishes TDD was still popular and stresses that TDD is a skill that must be developed. She describes the advantages of TDD, particularly in large applications, where having a robust test suite allows for faster development and less worry about breaking something inadvertently. [00:18:58] Andrew challenges the concept of TDD, suggesting that for a talented engineer, tests might seem like a waste of time.  Elise responds by emphasizing that TDD is a thinking tool that aids in understanding the problem. [00:20:59] The discussion turns to reviewing tests.  Elise explains her approach to reviewing pull requests by checking the problem solved, reviewing commits one at a time, and comparing her list of tests with the submitted ones, placing higher importance on the tests than the code itself. [00:24:02] Elise and Andrew compare their personal styles in reviewing code and the importance of preparing commit messages for review. Julie is curious how Elise and Andrew manage their commit history and whether they use the command line for combining commits. Andrew mentions using interactive rebase. [00:24:47] If you're interested in getting into TDD, Elise tells us she's working on a course about test driving in Rails applications coming out on early next year , but also recommends reading two great books: Test Driven Development: By Example by Kent Beck and 99 Bottles of OOP by Sandi Metz.[00:25:33] Julie questions how to handle TDD in a legacy codebase with complex and nested tests. Elise suggests pairing with someone more knowledgeable to break up the tests into smaller, more manageable files. Panelists:Andrew MasonJulie J.Guest:Elise ShafferSponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteElise Shaffer WebsiteElise Shaffer GitHubThe Ruby on Rails PodcastCircleCITest Driven Development: By Example by Kent Beck99 Bottles of OOP by Sandi Metz (00:24) - - Introduction and conference experience (01:39) - - Memorable conferences and tight-knit communities (02:45) - - In-person vs. online conferences (03:50) - - First conference experiences (06:12) - - Julie's rise in popularity and fame in the community (09:33) - - Testing and continuous integration in software development (12:46) - - Parallelized testing and speeding up test processes (13:56) - - Test Driven Development (TDD) and its applicability (15:30) - - Advantages of TDD and its role in understanding problems (18:58) - - Challenges to the concept of TDD (20:59) - - Reviewing tests and pull requests (24:02) - - Managing commit history and using interactive rebase (24:47) - - Recommendations for learning TDD (25:33) - - Handling TDD in legacy codebases

It's time for another Ruby on Rails podcast crossover episode! This time I'm joined by the RoR Podcasts new host, Elise Shaffer. Elise interviews me about the game show I've been giving, I offer my thoughts on doing "weird talks", and we chat about how I got started podcasting. We then flip the script and I interview Elise about her new course on Test Driven Development (TDD), her podcast, and her thoughts on teaching and learning. Elise also had some great tips for getting started (or getting better) with Vim.Links:The Ruby on Rails PodcastOriginal RoR crossover episode (Episode 4)Course hostingSupport the showReady to start your own podcast?This show is hosted on Buzzsprout and it's awesome, not to mention a Ruby on Rails application. Let Buzzsprout know we sent you and you'll get a $20 Amazon gift card if you sign up for a paid plan, and it helps support our show.SponsorsA big thanks to OBLSK for being the very first sponsor of the show!

Welcome to an adrenaline-pumping episode of The Mob Mentality Show! In this captivating installment, titled "Mastering the High Stakes Arena: A Story of Mobbing Under Pressure with Giovanni Asproni," we dive into the thrilling world of Mob Programming in high-pressure environments. Join us as we embark on an exploration of high stakes work, dissecting the very definition of what "high stakes" truly means. Giovanni Asproni takes us on a roller-coaster ride through his enthralling story of Mob Programming under the intense pressure of a high-stakes scenario.  Discover the challenges and triumphs faced during those critical first moments with a new team amidst a high-stakes project. Giovanni provides insights into the diverse skill sets and experience levels within and outside the mob, shedding light on whether the decision to mob was driven by the high stakes or not. Uncover the significance of bugs in high-stakes products, and the accessibility and security constraints in this specific situation. In the midst of high-stakes work, Giovanni emphasizes the unwavering commitment to quality, exemplified by full Test-Driven Development (TDD) and the art of story slicing. Delve into the world of unorthodox design for observability and the dynamics of decision-making in high-pressure mob settings. Explore the rapid shift to radical candor while the pressure mounts and learn strategies for managing stress within the ensemble. Giovanni shares his experiences of mobbing under pressure with unfamiliar team members, touching upon the role of a team/mob firewall/gatekeeper and the value of pairing during meetings. Gain insights into overcoming major challenges when mobbing versus working solo and the critical importance of the bus factor and resilience in high-stakes endeavors. Unearth the secrets behind maintaining high automation levels and Giovanni's epic 16-hour mobbing marathon learning Terraform. Discover the nuanced approach to TDD within the mob while having manual testing support outside of it. And yes, we even explore the surreal scenario of having a prime minister as a major stakeholder - you won't want to miss that story! Join us as we discuss their race against time to deliver and authentically demonstrate lean principles within the mob. Uncover the concept of "Productive Paranoia," and understand the impact of real vs. artificial crisis modes on work dynamics. Is it possible to channel the benefits of crisis-mode work into non-crisis projects without causing destruction? Giovanni shares his thoughts not only on this but also on coaching in a crisis and whether non-XP ways of working naturally lead to crises. Don't miss this high-energy, high-insight episode as we unravel the secrets of how a team mastered a high-stakes arena through Mob Programming. Tune in and immerse yourself in the world of ensemble teaming like never before!  Video and show notes: https://youtu.be/-tgjrd8sL2U 

Welcome to another exciting episode of the Mob Mentality Show! Today, we're diving into the fascinating world of MicroObjects with the creator himself, Quinn Gil. Prepare to unravel the intricacies of object-oriented programming practices taken to the next level. In this episode, we embark on an exploratory journey covering a multitude of key aspects: Mastering MicroObjects & OOP: Quinn guides us through the world of MicroObjects and how they dial up traditional object-oriented programming practices. SRP to the Extreme!: Quinn explains how MicroObjects takes the Single Responsibility Principle (SRP) to new heights, making emergent design and evolutionary architecture unavoidable. Ruthless Refactoring: Discover the art of ruthless refactoring - a key practice that MicroObjects emphasizes for keeping code highly resistant to code rot. Knowledge Transfer to Code: Learn effective methods for having a representation for every concept exist in the code. MicroObjects Principles Debated: Join us as we discuss many of the key MicroObjects principles including no 'new' inline, no primitives, composition over inheritance, no enums, no constructor logic, wrapping 3rd party code, and preventing yourself from doing bad things.  Persuading Others to Try MicroObjects: Quinn shares insights into effectively persuading your team to try MicroObjects, highlighting its benefits and advantages including stuff getting done faster. Defeating the Sunk Cost Fallacy: Understand to overcome the sunk cost fallacy with code, leading to better decision-making in development. TDD and Design Discovery: Explore the powerful synergy between Test-Driven Development (TDD) and design discovery, and how it can enhance your development process. Join us for an engaging conversation packed with wisdom and expertise, as we unravel the secrets of MicroObjects and its impact on software development. Whether you're a seasoned developer or just starting out, this episode offers valuable insights into optimizing your coding practices and elevating your projects to the next level. Tune in now to unlock the potential of MicroObjects! Video and show notes: https://youtu.be/W6C1C9i78Ec  

Join us on an enlightening journey into the world of software development internships in this episode of the Mob Mentality Show titled "The Intern Mob Chronicles." We sit down with Eduardo Lopez and Jeric Baga, who share their notable experiences and insights from their unique mob programming internship journey. Episode Highlights:

EP103 — TDD, testing y otras hierbas con Cecy GeraldoY repetimos el plato, pues nuevamente estamos con la tremenda Cecy Geraldo (Senior Consultant Developer en ThoughtWorks y “Chica Laboratoria”) para platicar sobre lo que realmente les importa a los Agile Teams que están en aquello del Desarrollo de SW.Platicaremos sobre Test Driven Development (#TDD), una de las prácticas de ingeniería más importante y tan antigua como el mismo concepto de Agilidad.¿Qué te puedes llevar de este episodio?: Revisaremos algo de la historia de TDD, su ciclo clásico, su papel en la ingeniería y en el día a día de los Agile Teams, sus beneficios y algunas criticas, su contexto con respecto a diferentes tipos de tests, la pirámide de automatización de tests, el modelo de trofeo para tests, consejos para principiantes, y para los no tan principiantes, todos basados en la experiencia.Hormigas del hormiguero en este episodio: Antonio Gallardo Burgos, Yohan Paez Maldonado, Gerald Valdés y Rodrigo Burgos Noceti.Si deseas conocer más sobre este episodio y todos los demás, visita el sitio: HormigasAgilistas.CL¡Gracias por ser parte del Universo de Hormigas Agilistas!#HormigasAgilistas #QueVivaLaAgilidad #Agile #Podcast #TDD #TestDrivenDevelopment #PirámideDeAutomatizaciónDelTesting #ModeloDeTrofeoDelTesting

Cecilia Geraldo y Javiera Laso, ambas Senior Developers de nuestra oficina de Chile, comparten una conversación fascinante donde explorarán temáticas clave del desarrollo de software y compartirán perspectivas sobre buenas prácticas como el pair programming y el Test Driven Development (TDD).    Además, discutirán la importancia de un ambiente de trabajo adecuado, la automatización consciente y cómo estas prácticas influyen en la calidad y estabilidad de los productos digitales, mientras comparten historias relacionadas con la falta de buenas prácticas en proyectos anteriores.

Get ready for an electrifying episode of DrunkenPM Radio as I welcome the esteemed James Grenning to unravel the world of Test Driven Development (TDD). Agile 2023 is just around the corner, and during the conference, James will be leading a workshop called "Your First Test-Driven Development." While TDD is not a new concept, it remains unfamiliar to many tech professionals who didn't come from a development background. That's precisely why I reached out to James and invited him to join me for this inspiring podcast. If you're immersed in Agile or managing technology projects, and TDD is still a mystery to you, this is a must-watch. TDD is a game-changer, and understanding it is crucial for your professional growth. I assure you that this episode will significantly impact your job in the best way possible. Now, let's talk about the best part of this podcast: our incredible guest, James Grenning. He personifies the epitome of old-school OG Agile Royalty. Not only is James one of the co-authors of the Agile Manifesto, but he also penned the definitive book on TDD. That's not all—James is the brilliant mind behind Planning Poker, a technique that has revolutionized Agile estimation. Stay tuned as we delve into this fascinating topic towards the end of our conversation. But wait, there's more! At the conclusion of our interview, James will unveil a remarkable system he designed and developed for his training classes. When off-the-shelf solutions fell short of meeting his requirements, James took matters into his own hands. His ingenuity and determination to deliver top-notch training are truly awe-inspiring. Don't miss out on this captivating podcast episode. James Grenning's wisdom and expertise will reshape the way you approach your work. Join me as we embark on a journey of discovery and empowerment with one of the brightest minds in the world of Test Driven Development. (This podcast was originally recorded using video. You can find that version here: https://youtu.be/k5OaxLCIzzI) James's Book Test Driven Development for Embedded C (Pragmatic Programmers): https://bit.ly/43CMsP0 James's session at Agile 2023 Your First Test-Driven Development at Agile 2023 https://events.agilealliance.org/Agile2023/session/1423798/your-first-test-driven-development-james-grenning Monday, July 24, 2023, 2:00 PM - 5:00 PM Lafayette 4 Contacting James Web: https://wingman-sw.com/about LinkedIn: https://www.linkedin.com/in/jwgrenning/ Twitter: https://twitter.com/jwgrenning Agile, Extreme Programming, XP, Scrum, TDD, Test Drive Development, James Grenning, Dave Prior, Reluctant Agilist, drunkenpm, Drunken PM Radio, Planning Poker, Estimation, Wingman-SW, Agile Development and Design Techniques,

2023-05-23 Weekly News - Episode 196Watch the video version on YouTube at https://youtube.com/live/3F5all2U5Pk?feature=share  Hosts:  Gavin Pickin - Senior Developer at Ortus Solutions Dan Card - Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our ReposStar all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Books 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Learn Modern ColdFusion (CFML) in 100+ Minutes - Free online https://modern-cfml.ortusbooks.com/ or buy an EBook or Paper copy https://www.ortussolutions.com/learn/books/coldfusion-in-100-minutes   Patreon Support (proficient)We have 40 patreons: https://www.patreon.com/ortussolutions. News and AnnouncementsAdobe ColdFusion 2023 released!!!!We are thrilled to announce the highly anticipated release of Adobe ColdFusion 2023!  Packed with cutting-edge features and enhanced performance, this release takes ColdFusion to new heights of innovation.Experience accelerated development, robust security measures, and seamless integration with modern technologies. From rapid application development to scalable enterprise solutions, Adobe ColdFusion empowers developers to build dynamic web applications with ease. Discover the limitless possibilities and stay ahead in the digital era.Upgrade to the latest version now and harness the true potential of ColdFusion. Elevate your coding experience with Adobe ColdFusion – the ultimate platform for unmatched productivity and success. LDAP and SAML integration Central Configuration Server GraphQL client HTML to PDF Cloud Services JWT integration in CF Whats new - https://helpx.adobe.com/coldfusion/using/whats-new.htmlhttps://coldfusion.adobe.com/2023/05/coldfusion2023-release/ ICYMI - Into the Box - Recap Keynote - Day 1 - https://t.co/42DozsZ0G9  Keynote - Day 2 - https://youtube.com/live/TOhOaNVy0dM Sessions Hands on Pre Conference Happy Box Hackathon New Releases and UpdatesLots of Releases So many - we are still waiting on the blogs and release notes for a lot of them, but ITB came with ColdBox7, CommandBox 5.9, Testbox 5, CBWire 3, Testbox CLI, Coldbox CLI, Quick, Qb, CBQ V1 and V2, cbDebugger 3, ContentBox 6 We will discuss some of them belowColdBox 7 ReleasedColdBox 7 has been released!  Install it via ForgeBox using `coldbox`.  Release at ITB 2023!What's New With ColdBox 7.0.0? Engine Support ColdBox CLI WireBox Updates Transient Request Cache Delegators Property Observers Lazy Properties New `onInjectorMissingDependency` event Population Enhancements (including mass assignment protection) Hierarchical Injectors (for Module Dependencies) Module Config Object Override files App Mode Helpers `redirectBack` included as `back` `DateTimeHelper` component Whoops! Upgrades More data for development REST exception responses JSON Pretty Printing in LogBox Output Exception Pretty Printing in LogBox Output Combine `canXXX` checks with logging using callback functions `event.setRequestTimeout()` - useful for testing https://coldbox.ortusbooks.com/v/7.x/intro/release-history/whats-new-with-7.0.0CBWIRE 3.0.0 ReleasedWe are very excited to announce the release of version 3 of CBWIRE, our ColdBox module that makes building modern, reactive apps a breeze. This version brings with it a new component syntax, 19 enhancements and bug fixes, and improved documentation. Our biggest goal with this release was to improve the developer experience and to provide a low barrier to entry to getting started with CBWIRE.https://www.ortussolutions.com/blog/cbwire-300-released  TestBox v5.0.0 Released!We are excited to announce the release of TestBox version 5, which brings a host of new features and improvements for developers. TestBox is a powerful and flexible tool that helps developers write comprehensive BDD/TDD tests for their applications, ensuring code quality and reducing the likelihood of bugs and errors. With TestBox v5, developers can take advantage of new features such as batch code coverage testing, improved reporting capabilities, method spies, and better integration with other tools in the Ortus suite.These new features make TestBox even more versatile and user-friendly, and provide developers with a powerful tool for building high-quality, reliable applications.https://www.ortussolutions.com/blog/testbox-v500-released FusionReactor 10 released, May 18If you're using FusionReactor, note that a new version 10 (10.0.0) released yesterday, May 18. While it's a new major release number, most of the items listed as new aren't really things that you will "see" as changed in the interface. I don't quite want to call it just "plumbing"--the folks had their reason to regard the new and changed features as warranting the major version number increase.https://www.carehart.org/blog/2023/5/19/fusionreactor_10_0_released/https://docs.fusion-reactor.com/release-notes/ ColdBox CLI 1.x ReleasedWe are thrilled to announce the release of our new ColdBox CLI tool! This powerful command-line interface is designed to help developers streamline their workflows and simplify their ColdBox development experience. With its intuitive syntax and powerful capabilities, the ColdBox CLI tool allows developers to easily create, test, and deploy ColdBox applications with just a few simple commands. Whether you are a seasoned ColdBox developer or just getting started with this powerful framework, the ColdBox CLI tool is the perfect addition to your toolkit.This tool used to be embedded in the CommandBox core, but it now has a new home (https://github.com/ColdBox/coldbox-cli) and can have it's own life-cycles including LTS support for our ColdBox Framework as well.https://www.ortussolutions.com/blog/coldbox-cli-1x-releasedICYMI - TestBox CLI 1.x ReleasedWe're excited to unveil our latest **TestBox CLI ** tool! This robust command-line interface is specifically crafted to assist developers in streamlining their workflows and enhancing their TestBox BDD/TDD development process. Boasting an intuitive syntax and potent functionalities, the TestBox CLI tool empowers developers to create, test, and generate reports on their ColdFusion (CFML) applications with ease, using only a handful of commands. Whether you're a seasoned ColdFusion (CFML) developer or a newcomer to this potent framework, the TestBox CLI tool is a valuable asset to add to your toolkit.This tool used to be embedded in the CommandBox core, but it now has a new home (https://github.com/ortus-solutions/testbox-cli) and can have it's own life-cycles.https://www.ortussolutions.com/blog/testbox-cli-1x-releasedNew Ortus Supported ORM Extension for Lucee.Other Releases: cbDedugger 3, ContentBox 6Webinar / Meetups and WorkshopsPOSTPONED - Adobe - Road to Fortuna Series: ColdFusion 2023 in Docker on Google Cloud PlatformMay 23, 2023 - MAYBE IN JUNE10 AM - 11 AM PTDuring GCP centric webinar, Mark Takata will explore how to run a containerized ColdFusion 2023 server on Google Cloud Platform's Kubernetes powered containerization system. He will demonstrate how the powerful new Google Cloud Platform features added to ColdFusion 2023 can help optimize application development, provisioning and delivery. This will be the first time ColdFusion 2023 will be shown running in containers publicly, and the session is designed to showcase the ease of working in this popular method of software delivery.Speaker - Mark Takata - ColdFusion Technical Evangelist, Adobehttps://docker-gcp-coldfusion.meetus.adobeevents.com/ CFCasts Content Updateshttps://www.cfcasts.comRecent Releases 2023 ForgeBox Module of the Week Series - 1 new Video https://cfcasts.com/series/2023-forgebox-modules-of-the-week  2023 VS Code Hint tip and Trick of the Week Series - 1 new Video https://cfcasts.com/series/2023-vs-code-hint-tip-and-trick-of-the-week  Just added 2019 Into the Box Videos Watch sessions from previous ITB years Into the Box 2022 - https://cfcasts.com/series/itb-2022  Into the Box 2021 - https://cfcasts.com/series/into-the-box-2021  Into the Box 2020 - https://cfcasts.com/series/itb-2020  Into the Box 2019 - https://cfcasts.com/series/into-the-box-2019  Coming Soon Into the Box 2023 Videos will soon be available for purchase as an EXCLUSIVE PREMIUM package. Subscribers will get access to premium packages after a 6 month exclusive window. More ForgeBox and VS Code Podcast snippet videos ColdBox Elixir from Eric Getting Started with Inertia.js from Eric 10 Testing Techniques by Dan? Feature Testing Deployment with Docker by Dan? Conferences and TrainingICYMI - Into the Box 2023 - 10th EditionMay 17-19, 2023 The conference will be held in The Woodlands (Houston), Texas - This year we will continue the tradition of training and offering a pre-conference hands-on training day on May 17th and our live Mariachi Band Party! However, we are back to our Spring schedule and beautiful weather in The Woodlands! Also, this 2023 will mark our 10 year anniversary. So we might have two live bands and much more!!!IN PERSON ONLY https://intothebox.orghttps://itb2023.eventbrite.com/ Can't wait? Watch videos from the last 4 years on CFCasts Into the Box 2022 - https://cfcasts.com/series/itb-2022  Into the Box 2021 - https://cfcasts.com/series/into-the-box-2021  Into the Box 2020 - https://cfcasts.com/series/itb-2020  Into the Box 2019 - https://cfcasts.com/series/into-the-box-2019  THIS WEEK - VueConf.usNEW ORLEANS, LA • MAY 24-26, 2023Jazz. Code. Vue.Workshop day: May 24Main Conference: May 25-26https://vueconf.us/ CFCamp - Pre-Conference - Ortus has 4 TrainingsJune 21st, 2023Held at the CFCamp venue at the Marriott Hotel Munich Airport in Freising. Eric - TestBox: Getting started with BDD-TDD Oh My! Luis - Coldbox 7 - from zero to hero Dan - Legacy Code Conversion To The Modern World Brad - CommandBox Server Deployment for the Modern Age https://www.cfcamp.org/pre-conference.html CFCampJune 22-23rd, 2023Marriott Hotel Munich Airport, FreisingCheck out all the great sessions: https://www.cfcamp.org/sessions.htmlCheck out all the great speakers: https://www.cfcamp.org/cfcamp-conference-2023/speakers.html Register now: https://www.cfcamp.org/THAT ConferenceHowdy. We're a full-stack, tech-obsessed community of fun, code-loving humans who share and learn together.We geek-out in Texas and Wisconsin once a year but we host digital events all the time.WISCONSIN DELLS, WI / JULY 24TH - 27TH, 2022A four-day summer camp for developers passionate about learning all things mobile, web, cloud, and technology.https://that.us/events/wi/2023/Our very own Daniel Garcia is speaking there https://that.us/activities/R3eAGT1NfIlAOJd2afY7Adobe CF Summit WestLas Vegas 2-4th of October.Get your early bird passes now. Session passes @ $99 Professional passes @ $199. Only till May 31st, 2023!Can you spot ME - Gavin - Apparently I'm in 3 of the photos!Call for Speakers is OPENhttps://cfsummit.adobeevents.com/ https://cfsummit.adobeevents.com/speaker-application/Ortus Training - ColdBox Zero to HeroDates and VenueMore conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week5/10/23 - Blog - Ben Nadel - Using BugSnag As A Server-Side Logging Service In ColdFusionI've been on the lookout for a better error logging service; and, over on Facebook, Jay Bronson recommended that I look at BugSnag. They have a free-tier, so I signed up to try it out. And, I must say, I'm very pleased with the User Interface (UI) and the basic functionality. That said, I could not get the Java SDK (Software Development Kit) working with JavaLoader. As such, I hacked together some ColdFusion code that would do just enough to send data to the BugSnag API. What I have is far from feature complete; but, I thought it might be worth sharing.https://www.bennadel.com/blog/4462-using-bugsnag-as-a-server-side-logging-service-in-coldfusion.htm 5/11/23 - Blog - Luis Majano - TestBox v5.0.0 Released!We are excited to announce the release of Testbox version 5, which brings a host of new features and improvements for developers. TestBox is a powerful and flexible tool that helps developers write comprehensive BDD/TDD tests for their applications, ensuring code quality and reducing the likelihood of bugs and errors. With TestBox v5, developers can take advantage of new features such as batch code coverage testing, improved reporting capabilities, method spies, and better integration with other tools in the Ortus suite.These new features make TestBox even more versatile and user-friendly, and provide developers with a powerful tool for building high-quality, reliable applications.https://www.ortussolutions.com/blog/testbox-v500-released5/12/23 - Blog - Brian - Why You Don't Want To Use CFMX_COMPAT EncryptionThis is the first of what may be a couple of posts about my presentation from ColdFusion Summit East 2023, which was held in April in Washington, DC.Let's talk about ColdFusion and encryption.  Specifically -- about the CFMX_COMPAT algorithm.  The encrypt() function was introduction in ColdFusion 4 (ca. November 1998), and CFMX_COMPAT was the only algorithm available.  The release of ColdFusion 7 (ca. February 2005) added native support for AES, 3DES, DES, and Blowfish.  But CFMX_COMPAT remains the default algorithm used by the encrypt() function.   https://hoyahaxa.blogspot.com/2023/05/why-you-dont-want-to-use-cfmxcompat.html 5/13/23 - Blog - Nolan Erck - Speaking at Into The Box 2023It's official...next week I'll be speaking at Into The Box in Houston!If you're not already familiar with it, Into The Box is the most modern leaning conference for CFML! But really the CFML-specific portion is complimented by a heavy dose of content that is applicable to many other platforms. A quick look at the agenda will show you sessions ranging from web security, to AWS pub/sub mechanisms, to OAuth and more!https://southofshasta.com/blog/speaking-at-into-the-box-2023/ 5/14/23 - Blog - Ben Nadel - Maintaining White Space Using jSoup And ColdFusionjSoup is a Java library for parsing and manipulating HTML strings. For the last few years, I've been using jSoup to clean-up and normalize my blog posts. And now, I'm looking to use jSoup to help me transform and cache GitHub Gists. At the time of this writing, Gist code is rendered in an HTML with cells that use white-space: pre as the means of controlling white space output. jSoup doesn't parse the CSS; so, it does understand that it needs to maintain this white space when serializing the document back into HTML. If we want to keep this white space in the resultant document, we have to disable pretty printing.https://www.bennadel.com/blog/4463-maintaining-white-space-using-jsoup-and-coldfusion.htm5/16/23 - Blog - Adobe ColdFusion Portal - Introducing the 2023 Release of Adobe ColdFusionWe are thrilled to announce the highly anticipated release of Adobe ColdFusion 2023!  Packed with cutting-edge features and enhanced performance, this release takes ColdFusion to new heights of innovation.https://coldfusion.adobe.com/2023/05/coldfusion2023-release/ 5/16/23 - Blog - Luis Majano - Ortus Solutions - ColdBox 7.0.0 ReleasedIntroducing ColdBox 7: Revolutionizing Web Development with Cutting-Edge Features and Unparalleled PerformanceWe are thrilled to announce the highly anticipated release of ColdBox 7, the latest version of the acclaimed web development HMVC framework for ColdFusion (CFML). ColdBox 7 introduces groundbreaking features and advancements, elevating the development experience to new heights and empowering developers to create exceptional web applications and APIs.Designed to meet the evolving needs of modern web development, ColdBox 7 boasts a range of powerful features that streamline the development process and enhance productivity. With its robust HMVC architecture and developer-friendly tools, ColdBox 7 enables developers to deliver high-performance, scalable, and maintainable web applications and APIs with ease.https://www.ortussolutions.com/blog/coldbox-700-released 5/16/23 - Blog - Ben Nadel - Parsing GitHub Gist Embeds Into A Normalized Data Structure Using jSoup In ColdFusionAs I mentioned yesterday, I've been using GitHub Gists to add the syntax highlighting / formatting in my blog post content. This has been working great; but, I've never liked the idea of having to reach out to a 3rd-party system at render time in order to provide my full content experience. As such, I've been considering ways to cache the GitHub Gist data locally (in my system) for both better control and better performance. Unfortunately, GitHub Gists aren't provided in the most user-friendly format. To that end, we can use jSoup in ColdFusion to read-in, parse, and normalize the Gist contents.https://www.bennadel.com/blog/4464-parsing-github-gist-embeds-into-a-normalized-data-structure-using-jsoup-in-coldfusion.htm 5/16/23 - Blog - Nolan Erck - My Into The Box 2023 ScheduleInto The Box 2023 starts tomorrow! After a flight that included several delay, I finally arrived at the hotel a few minutes ago. As per usual, there is a ton of great content this year; deciding which sessions to attend is like the techie equivalent of Sophie's Choice! Here's my best guess as to where you can find me:Wednesday: Async Programming & Scheduling workshophttps://southofshasta.com/blog/my-into-the-box-2023-schedule/ 5/17/23 - Blog - Charlie Arehart - ColdFusion 2023 released, May 17 2023: resources and thoughtsColdFusion 2023 has been released today, May 17 2023. For more on the many features, see the following several Adobe blog posts and substantial documentation resources they released also today, about which I offer some additional comment below.I also discuss changes in OS support (saving you having to compare the docs discussing that), as well as the change to CF2023 running on Java 17 (which you could miss, as it's not highlighted by Adobe in any of the announcement resources.) I also discuss changes in the licensing document/EULA (again, to save you having to do that comparison), as well as an observation about pricing (it has not changed since CF2021).I also discuss some migration considerations and close by pointing out the Hidden Gems in CF2023 talk that I did, based on the prerelase. I plan to update that in time based on this final release.https://www.carehart.org/blog/2023/5/17/cf2023_released/ 5/18/23 - Blog - Ben Nadel - Using CSS Flexbox To Create A Simple Bar Chart In ColdFusionI'm a huge fan of CSS Flexbox layouts. They're relatively simple to use and there's not much to remember in terms of syntax. One place that I love using Flexbox is when I need to create a simple bar chart. I don't do much charting in my work, so I never have need to pull in large, robust libraries like D3. But, for simple one-off visualizations, CSS Flexbox is my jam. I thought it might be worth sharing a demo of how I do this in ColdFusion.https://www.bennadel.com/blog/4466-using-css-flexbox-to-create-a-simple-bar-chart-in-coldfusion.htm 5/18/23 - Blog - Charlie Arehart - FusionReactor 10 released, May 18: resources and thoughtsIf you're using FusionReactor, note that a new version 10 (10.0.0) released yesterday, May 18. While it's a new major release number, most of the items listed as new aren't really things that you will "see" as changed in the interface. I don't quite want to call it just "plumbing"--the folks had their reason to regard the new and changed features as warranting the major version number increase.For more, read on.Of course, I had just last week blogged on the release of FR 9.2.2, released March 1. I'm not letting as much time pass with this post. :-)https://www.carehart.org/blog/2023/5/19/fusionreactor_10_0_released/5/22/23 - Blog - Grant Copley - CBWIRE 3.0.0 ReleasedWe are very excited to announce the release of version 3 of CBWIRE, our ColdBox module that makes building modern, reactive apps a breeze. This version brings with it a new component syntax, 19 enhancements and bug fixes, and improved documentation. Our biggest goal with this release was to improve the developer experience and to provide a low barrier to entry to getting started with CBWIRE.https://www.ortussolutions.com/blog/cbwire-300-released CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 67 ColdFusion positions from 43 companies across 32 locations in 5 Countries.4 new jobs listed this weekFull-Time - ColdFusion Programmer at Tulsa, OK - United States May 23https://www.getcfmljobs.com/jobs/index.cfm/united-states/ColdFusion-Programmer-at-Tulsa-OK/11575 Full-Time - ColdFusion Engineer at Remote - United States May 21https://www.getcfmljobs.com/jobs/index.cfm/united-states/ColdFusionEngineer-at-Remote/11574 Full-Time - ColdFusion Lead at Pune, Maharashtra - India May 11https://www.getcfmljobs.com/jobs/index.cfm/india/ColdFusion-Lead-at-Pune-Maharashtra/11573 Full-Time - ColdFusion Developer at Pune, Maharashtra - India May 09https://www.getcfmljobs.com/jobs/index.cfm/india/ColdFusion-Developer-at-Pune-Maharashtra/11571 Other Job LinksThere is a jobs channel in the CFML slack team, and in the Box team slack now tooForgeBox Module of the WeekTestBoxTestBox is a Behavior Driven Development (BDD) and Test Driven Development (TDD) framework for ColdFusion (CFML). It also includes mocking and stubbing capabilities via its internal MockBox library.V5 Release NotesWe are excited to announced the release of Testbox version 5, which brings a host of new features and improvements for developers. TestBox is a powerful and flexible tool that helps developers write comprehensive BDD/TDD tests for their applications, ensuring code quality and reducing the likelihood of bugs and errors. With TestBox v5, developers can take advantage of new features such as batch code coverage testing, improved reporting capabilities, method spies, and better integration with other tools in the Ortus suite.These new features make TestBox even more versatile and user-friendly, and provide developers with a powerful tool for building high-quality, reliable applications. You can read more about TestBox in our comprehensive documentation online: https://testbox.ortusbooks.com/ https://www.forgebox.io/view/testbox VS Code Hint Tips and Tricks of the WeekVisual Studio Code Remote - SSH - PreviewBy Microsoft The Remote - SSH extension lets you use any remote machine with a SSH server as your development environment. This can greatly simplify development and troubleshooting in a wide variety of situations. You can:Develop on the same operating system you deploy to or use larger, faster, or more specialized hardware than your local machine.Quickly swap between different, remote development environments and safely make updates without worrying about impacting your local machine.Access an existing development environment from multiple machines or locations.Debug an application running somewhere else such as a customer site or in the cloud.No source code needs to be on your local machine to gain these benefits since the extension runs commands and other extensions directly on the remote machine. You can open any folder on the remote machine and work with it just as you would if the folder were on your own machine.https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-sshWorks well with: Visual Studio Code Remote - SSH: Editing Configuration Fileshttps://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh-edit Thank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website All Patreon supporters have their own Private Channel access BoxTeam Slack https://community.ortussolutions.com/Top Patreons (proficient) John Wilson - Synaptrix Tomorrows Guides Jordan Clark Gary Knight Mario Rodrigues Giancarlo Gomez David Belanger  Dan Card Jeffry McGee - Sunstar Media Dean Maunder Nolan Erck  Abdul Raheen And many more PatreonsYou can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors Thanks everyone!!! ★ Support this podcast on Patreon ★

Have you ever wondered why some teams struggle to adopt Test-Driven Development (TDD) while others excel at it? Join us in this thought-provoking episode as we delve into the challenges of crossing the TDD chasm and explore testing strategies with the insightful Khaled Souf. Are you tired of "freestyling" with no tests? Do you find TDD too hard? We address these questions and more as we discuss the human side of trying to adopt TDD and respond to resistance along the way. Discover the power of supportive guidance and learn how to create an environment where teams can thrive and contribute. But that's not all – we also dive into the world of ensemble programming and the traps that teams often encounter. From the "No Safe Space Trap" to the "Big Steps Trap," we uncover the obstacles that can hinder progress. Find out how to establish lean flow and minimize waste within an ensemble, and explore the balance between strict equality of navigation and minimum viable silence. We also explore the synergy of legacy code and Domain-Driven Design (DDD), showcasing how DDD can be applied while fixing bugs. Don't miss this engaging conversation packed with insights, practical advice, and real-world examples. Subscribe now to our podcast and YouTube channel to be notified when episodes are released. Video and Show Notes: https://youtu.be/XFHzZMlckzU 

BONUS: Helping Scrum Masters build empathy towards team members with J.B. Rainsberger Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   About J.B. Rainsberger JB is a seasoned software developer, consultant, and trainer based in Canada, known for his expertise in Test-Driven Development (TDD). With his extensive knowledge and experience in the field, he authored the acclaimed course "The World's Best Intro to TDD" and actively contributes to the community through his blog "The Code Whisperer." JB is a sought-after speaker and has been invited to present at numerous events worldwide. In addition to his passion for software development, he is also a skilled Bowling player. JB's diverse set of skills and experiences help him inspire and empower fellow developers through his work. You can link with J.B. Rainsberger on LinkedIn, visit his home on the net at JBrains.ca, and even ask him questions at ask.JBrains.ca.  If you want to know more about his offer, and get support from JB, you can visit experience.JBrains.ca.

I avsnitt 42 av Utveckla snackar vi TDD – Test Driven Development – med Kristofer Linnestjerna, systemutvecklare på Consid Göteborg!  Vad är TDD, varför använder man det, när passar det, när är det mindre lämpligt, vilka verktyg kan man ta hjälp av och var börjar man som fullkomlig gröngöling? Dessa frågor, och många fler, får vi svar på i det här avsnittet. Dessutom avslöjar Kristofer hemligheten bakom riktigt välgrillad kyckling och hur han fick en hel Erasmus-klass att gapa av förvåning i Aberdeen. Tidskoder: 0.31 Programledare Simon Zachrisson och Lily Tsui hälsar hej och välkomna och delar med sig av sina bästa tält-tips. 5.44 Dagens ämne: TDD. 7.13 Välkommen dagens gäst: Kristofer Linnestjerna! 7.51 Detta är TDD – Kristofer gör en kort hisspitch. 8.32 Så använder Kristofer TDD. 9.21 Kristofer berättar om sin snabbt avklarade karriär i TV4:s Grillmästarna och avslöjar hur man grillar kyckling utan att det blir torrt. 11.57 Så kom Kristofer in i utvecklingsbranschen. 12.36 Kristofer berättar om sitt Erasmus-utbyte i Aberdeen och hur han chockade sina kurskamrater. 14.28 Så gick det till när Kristofer började jobba med TDD. 16.44 Så kan ett exempeltest se ut. 18.55 Dessa har lätt att ta till sig TDD-tänket. 20.11 Vilka testmönster ryms inom TDD-begreppet? 20.50 Om test-täckning. 23.15 Leder TDD till mer läsbar kod? 24.45 Vad kan ett enskilt test ha för metodnamn? 25.40 Dessa produkter kan man använda. 28.35 Detta är FakeItEasy. 32.06 Så säljer Kristofer in TDD till kollegor och beställare. 32.41 Måste alla i ett projekt vilja köra TDD för att det ska funka? 33.02 Så motiverar man för kund att arbetssättet kommer ta mer tid, i början. 34.29 Simon mansplainar isbergsprincipen. 35.04 Dessa vanliga missuppfattningar om TDD möter Kristofer på jobbet. 36.18 Detta är den vanligaste bakgrunden hos dem som jobbar med TDD. 37.26 Så jobbar man med TDD i agila team. 38.32 Så involverar man kravställaren i TDD. 39.04 När är ett problem för omfattande för att det ska funka med TDD? 41.56 När är det olämpligt att använda TDD? 43.01 Så kommer sättet man jobbar med enhetstester utvecklas framöver. 44.02 Dessa verktyg är bra att använda för den som vill komma igång med TDD. 44.49 Så kommer du igång. 46.39 Tusen tack Kristofer! 47.03 Simon och Lily debriefar, försöker sammanfatta vad de har lärt sig och uppmanar lyssnarna att höra av sig med tips och önskemål om ämnen och gäster på utveckla@consid.se eller på instagram @utvecklapodcast. 52.18 Tack och hej! Intressanta länkar: https://www.adlibris.com/se/bok/clean-code-9780132350884 https://xunit.net/ https://nunit.org/ https://fakeiteasy.github.io/ https://fluentassertions.com/

Mario Hyland, Senior Vice President and Founder of AEGIS, has more than 30 years supporting Information Technology having a variety of roles and responsibilities. Mr. Hyland initially served the Pharmaceutical Industry in the capacity of Product Developer/Manager for a Call Reporting system with more than 120 Pharma companies across Canada and the U.S. Mr. Hyland was instrumental in coordinating and forming a Pharmaceutical (Walsh Marketing) industry collaboration and steering committee. Mr. Hyland served as a member of the Litton Systems Guidance Division, where he participated in Testing that served to address numerous Engineering Change Orders (ECO) associated with the performance and accuracy of the U.S. Cruise Missile System in U.S. Department of Defense (DoD) program. Mr. Hyland has taken this experience of driving better testing practices to a number of industry engagements with AEGIS. Mr. Hyland's duties have included a broad range of Executive Leadership, Board and Advisory services, and Global Operations, including financial, budgeting, and marketing duties. Mr. Hyland has been a board member of industry organizations such as Application Service Providers (ASP) Executive Consortium, the HL7 ARB, and various HIMSS Chapters. Mr. Hyland's focus on testing was spawned by a desire to ensure "PRODUCTION" systems have the highest data quality as possible. By leveraging this Test-First approach, Mr. Hyland has seen AEGIS engage with MCI/WorldCom (FTS2001 - 65,000 concurrent users), US Army AKO (Army Knowledge Online - 2M concurrent users), and the Department of Veterans Affairs (VA) My HealtheVet program. Mr. Hyland's introduction to Health IT standards first began with the VA, and HL7 V2 (MLLP) with VistA. With Dr. Kolodner's (formerly VA Executive Director My HealtheVet) appointment to the Office of the National Coordinator for Health Information Technology (ONC), Mr. Hyland and AEGIS were engaged to support several IHE Profiles, and the NHIN (predecessor to eHEX) National Exchange. While working with the VA, DoD, ONC and other federal partners in support of VLER, Mr. Hyland advanced the concept of Standards based development to align with cloud testing services with the Developers Integration Lab (DIL). Through the DIL, more than 500 Organizations including vendors, implementers, and exchange participants were able to self-service and test conformance 24x7x365 to ensure continuous interoperability. Mr. Hyland led AEGIS efforts on the DIL and leveraged that program level experience to advance the Touchstone project, a cloud platform designed to support FHIR implementations around the globe. Touchstone is a Test-Driven-Development (TDD) environment which engages the community from the early stages of standards development, through early-adopters, and wide-industry adoption. Touchstone currently supports programs like Da Vinci, CARiN Alliance CARiN BB, Ontario Health, Nictiz, and Medcom (to name a few). Mr. Hyland was recently recognized as a Federal Health IT Top 100 Executive for 2022, an award issued in collaboration with HHS, the Department of Defense and the Department of Veterans Affairs. Mr. Hyland continues to speak about the benefits of standards based approaches to Interoperability, including leveraging HL7 Standards such as FHIR and numerous Implementation Guides (IG's). Mr. Hyland's desire to support the HL7 FHIR FAST Accelerators in the role of Steering Committee member will be to leverage his experience with the NHIN and other national exchange and information sharing networks to ensure FHIR continues to offer the community a reliable and robust "Continuously Interoperable" platform “At-Scale” for better Patient Care Coordination by accelerating adoption, reducing burden for implementers, and ensuring the highest level of standards compliance across the Integrated Ecosystem.

You may have heard of London style Test Driven Development (TDD).  You also may have heard of Detroit or Chicago style TDD. However, what do these two styles look like "out in the wild" in real production code? How about on teams collaborating via Ensemble Programming? Come join Chris and Austin as they share about their mob programming experiences of London TDD and Detroit/Chicago TDD. They not only talk about the pros and cons of each style in practice but they also talk about when they have seen each style done well and each style done poorly. Then they get practical about when to "shift gears" to experiment with a different style to fit the situation of the code and the team/mob. Video and Show Notes: https://youtu.be/n3thEwckXIs 

Shai Yalin is a freelance software architect and mentor. He specializes in teaching organizations and individuals how to use Test Driven Development (TDD) and other development methodologies and best practices. In this episode Shai joins us to explain how to use these methods in order to create software that is resilient to change, and how to refactor existing brittle code in order to clean out the rot.Sponsors Top End Devs Coaching | Top End Devs Links Chronomatic: my side-project story Your Software as a Kitchen The Anatomy Of A Rotten Codebase LinkedIn: Shai Yallin Twitter: @shaiyallin Picks AJ - Read The Lost Metal by Brandon Sanderson: Prologue and Chapters One and Two Dan - Fargo Shai - Vitest Shai - We Are Legion (We Are Bob) (We Are Bob) (Bobiverse, #1) Shai - Citizen Of Glass, by Agnes Obel Steve- GitHub Copilot investigation · Joseph Saveri Law Firm & Matthew Butterick Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacy

Shai Yalin is a freelance software architect and mentor. He specializes in teaching organizations and individuals how to use Test Driven Development (TDD) and other development methodologies and best practices. In this episode Shai joins us to explain how to use these methods in order to create software that is resilient to change, and how to refactor existing brittle code in order to clean out the rot.Sponsors Top End Devs Coaching | Top End Devs Links Chronomatic: my side-project story Your Software as a Kitchen The Anatomy Of A Rotten Codebase LinkedIn: Shai Yallin Twitter: @shaiyallin Picks AJ - Read The Lost Metal by Brandon Sanderson: Prologue and Chapters One and Two Dan - Fargo Shai - Vitest Shai - We Are Legion (We Are Bob) (We Are Bob) (Bobiverse, #1) Shai - Citizen Of Glass, by Agnes Obel Steve- GitHub Copilot investigation · Joseph Saveri Law Firm & Matthew Butterick

This is the third and final installment of a 3-part series where Joe Alaimo and Andy Rallis discuss the different types of software testing, what they are, how they are performed and ways that they apply to the software development that actuaries are involved in.  Full Description: Have you ever been involved with a software development project?  One thing that all software development projects have in common is testing.  You may have been involved in some of the testing of these systems or maybe you were in meetings where testing was discussed or perhaps you are interested in doing more testing in the work that you are doing.  You may have heard some terms such as unit testing, integration testing and functional testing but are not sure what the differences are. You may also not work with software development but want to understand elements of software testing so that you can apply them to your actuarial work. In this final installment of a 3-part series, Joe Alaimo and Andy Rallis cover related topics to software testing: Continuous Integration/Continuous Delivery (CI/CD), How to write a test, Test Driven Development (TDD), and Agile's relationship to testing. The two explain what each topic is, how each topic relates to the types of testing discussed in earlier installments and why each topic is important. They also discuss considerations and tradeoffs when thinking through implementing CI/CD, TDD or Agile testing. Links to the tools discussed in the podcast: GitHub – The most popular code repository (owned by Microsoft) https://github.com TravisCI – An early build and test running service for code https://www.travis-ci.com TestPad – A tool for test case management https://ontestpad.com

Zur Erhöhung der Softwarequalität denken viele über den Einsatz der Test-driven Development (TDD) Methode im Entwicklungsprozess nach. Aber warum sieht man diese Methode in der Praxis nur selten im Einsatz? In dieser Folge sprechen wir über die Methode, was wir davon halten und darüber warum sie unserer Meinung nach häufig nur teilweise zum Einsatz kommt. Ihr wollt uns etwas Gutes tun? Spendiert uns gerne einen Kaffee: www.buymeacoffee.com/todocast Links: TDD auf Wikipedia (deutsch): https://de.wikipedia.org/wiki/Testgetriebene_Entwicklung Twitter-Thread zum Thema: https://twitter.com/robinmanuelt/status/1570402637568217088 Video "Test Driven Development (TDD)" mit David Tielke: https://youtu.be/Q7IacWtNaG0 Video "Warum TDD (Test-Driven Development) überbewertet ist" mit Golo Roden: https://youtu.be/YUm4P2b0YPI Malte auf Twitter: twitter.com/MalteLantin Robin-Manuel auf Twitter: twitter.com/robinmanuelt Feedback und Anregungen: todopodcast@outlook.com

What is Test-Driven Development (TDD)_ Agile Basics for PMI-ACP & PMP

In this episode, we'll start by separating out Agile from DevOps, and then bringing in CI/CD pipelines.  We'll also discuss DevSecOps and some of the best practices in engineering that a developer can adopt. We'll also give an overview of what a CI/CD pipeline looks like, what a pipeline stage is, what a pipeline's purpose is, and how it is related to DevOps.  As a bonus, I talk about tools for Static Code Analysis (SCA) and Static Application Security Testing (SAST)!  We'll also touch on Test Driven Development (TDD).  ----- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Storytime with Dad Podcast

SponsorsAudible - get a free audiobook from Audible with no strings attached at https://workingcode.dev/audibleTesting code is like taking out insurance: until you need it, it can be hard to understand why it's so important; it can be hard to understand what everyone is raving about. And so, you continue writing your code without tests. And, everything is fine, until one day it isn't. And in that moment, you finally see for yourself what value automated testing could have brought to the table.On today's show, the crew talks to Scott Stroz about his experience with Test Driven Development (TDD); and, about how he has come to understand that testing makes possible what would have otherwise been impossible. With solid testing practices in place, Scott was able to refactor an exceedingly convoluted intake form that rendered 25 buttons, 6 unique workflows, and took the user through up to 28 steps. Crunch those numbers and try telling me that the chance of making a mistake isn't absolute. And yet, thanks to a rigorous test-first coding methodology, Scott was able to completely refactor this workflow - from the ground-up - and delivery it on-time and without error!Notes & LinksSandi Metz: RailsConf 2014 - All the Little ThingsSandi Metz: No Private MethodsFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.

In this installment of Programming By Stealth, Bart Busschots finishes firming up our foundation on a few more things before we meet Jest, which will be the Test Driven Development (TDD) environment we'll be learning next time. He explains in some adorable examples involving a parrot (named Polly of course) how getters can be used to construct short but powerful syntaxes that seem quite counterintuitive at first glance. These are heavily used by Jest, and without learning about them, they would simply look like magic. He said some purists may see this syntax as an abuse of getters but it's a pretty slick method that yields very readable APIs. The second thing he teaches us is that functions can actually return functions. That sounds like opening a hole in the space-time continuum but it's actually quite logical and useful as Bart explains the usefulness of this really well. No parrots involved, but lots of pancakes and waffles in his examples. You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.

In this installment of Programming By Stealth, Bart Busschots finishes firming up our foundation on a few more things before we meet Jest, which will be the Test Driven Development (TDD) environment we'll be learning next time. He explains in some adorable examples involving a parrot (named Polly of course) how getters can be used to construct short but powerful syntaxes that seem quite counterintuitive at first glance. These are heavily used by Jest, and without learning about them, they would simply look like magic. He said some purists may see this syntax as an abuse of getters but it's a pretty slick method that yields very readable APIs. The second thing he teaches us is that functions can actually return functions. That sounds like opening a hole in the space-time continuum but it's actually quite logical and useful as Bart explains the usefulness of this really well. No parrots involved, but lots of pancakes and waffles in his examples. You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the code is improved so that the tests pass. This is opposed to software development that allows code to be added that is not proven to meet requirements.https://code.tutsplus.com/tutorials/beginning-test…https://rubikscode.net/2019/03/04/test-driven-deve…Linkedin Feel free to contact me.

Do you write unit tests? Do you use Test Driven Development (TDD)? Dennis Doomen does. He started an open source project called Fluent Assertions thirteen years ago that now has over 100 million downloads and has been forked over 400 times. We talk to Dennis about how Fluent Assertions got started and how it has evolved over the years. Dennis is a big proponent of TDD so we talk through some of the positives and negatives of using the methodology. Unit tests are something that most developers want to incorporate into their workflow but can't for one reason or another. Join us for this episode and maybe Dennis will be able to help you get over that hump. Are unit tests part of your workflow? Let us know on Twitter at @dotnet_Podcast. Panel Caleb WellsShawn Clabough Guest Dennis Doomen Sponsors Dev Influencers AcceleratorRaygun | Click here to get started on your free 14-day trialLevel Up | Devchat.tv Links The Continuous ImproverFluent AssertionsC# Coding GuidelinesTwitter: Dennis "Mr Fluent Assertions" Doomen ( @ddoomen ) Picks Caleb- Wonder Woman 1984Dennis- Shang-Chi and the Legend of the Ten RingsDennis- Death StrandingShawn- Halloween Shawn- MostlyDead Contact Caleb: Caleb Wells CodesTwitter: Caleb Wells (@calebwellscodes)Linkedin: Caleb WellsFacebook: Caleb Wells Contact Shawn Twitter: Shawn Clabough (DotNetSuperhero) Special Guest: Dennis Doomen.

What is Test Driven Development (TDD) and why is it so useful? Learn how to use TDD to speed up your software development.

Rosemary Wang joins the adventure to dive into a discussion on what Infrastructure as Code is and how to begin thinking about what it is and how it goes together. She focuses on maintainability, security, and reliability. Panel Jeffrey Groman Will Button Guest Rosemary Wang Sponsors Dev Influencers Accelerator Links Essential Infrastructure as Code Scaling Infrastructure as Code to Improve Delivery & Maintain Security - YouTube Testing HashiCorp Terraform Workshop: Exploring Policy as Code for Cloud Infrastructure - YouTube HashiCorp Presents at Security Field Day 5 Test-Driven Development (TDD) for Infrastructure LinkedIn: Rosemary Wang GitHub: Rosemary Wang ( joatmon08 ) Twitter: Rosemary Wang ( @joatmon08 ) Picks Jeffrey- Eco Dual-Motor Adjustable Height Sit/Stand Desk Rosemary- Essential Infrastructure as Code Will- Evodesk Contact Jeffrey: Groman Cyber Contact Will: DevOps For Developers Twitter: Will Button ( @wfbutton )

Rosemary Wang joins the adventure to dive into a discussion on what Infrastructure as Code is and how to begin thinking about what it is and how it goes together. She focuses on maintainability, security, and reliability. Panel Jeffrey Groman Will Button Guest Rosemary Wang Sponsors Dev Influencers Accelerator Links Essential Infrastructure as Code Scaling Infrastructure as Code to Improve Delivery & Maintain Security - YouTube Testing HashiCorp Terraform Workshop: Exploring Policy as Code for Cloud Infrastructure - YouTube HashiCorp Presents at Security Field Day 5 Test-Driven Development (TDD) for Infrastructure LinkedIn: Rosemary Wang GitHub: Rosemary Wang ( joatmon08 ) Twitter: Rosemary Wang ( @joatmon08 ) Picks Jeffrey- Eco Dual-Motor Adjustable Height Sit/Stand Desk Rosemary- Essential Infrastructure as Code Will- Evodesk Contact Jeffrey: Groman Cyber Contact Will: DevOps For Developers Twitter: Will Button ( @wfbutton )

We discuss how Test Driven Development (TDD) can help you write better code, and build better software. Packed with tips and tricks, gotchas and best practices, the panel explore the subject and share their real-world experiences.

We discuss how Test Driven Development (TDD) can help you write better code, and build better software. Packed with tips and tricks, gotchas and best practices, the panel explore the subject and share their real-world experiences.

We discuss how Test Driven Development (TDD) can help you write better code, and build better software. Packed with tips and tricks, gotchas and best practices, the panel explore the subject and share their real-world experiences.

In this month's “Two Points of View at Two” session, Rex welcomes Gio Lodi to discuss how to adopt a Test-Driven Development mindset followed by a Q&A opportunity. We changed the start time of this month's webinar to 5:00 PM Central in order to allow for this multi-continent session. After all, it's 2 o'clock somewhere! Test-Driven Development (TDD), is a software development technique that flips the testing process on its head: rather than testing after the product is done, developers build tests first and use the failure as a guide to write the necessary code. TDD's immediate benefit is that it gives better test coverage, but there are more beneficial second order effects that come when applying it consistently. Moving in this step-by-step, feedback driven process improves the team productivity and results in a malleable software design. In this presentation, we'll look at how to bring this mindset that focuses on iteration and feedback in all the areas of software and product development. Gio Lodi is the author of Test-Driven Development in Swift. He's been exploring testing and automation since 2011, when he encountered TDD while working on a startup with his University housemates. Gio publishes his findings in his blog and with presentations such as this one. He lives in an Australian beach town with his wife and two little children, and works remotely as mobile infrastructure engineer at Automattic, where he helps teams working on apps such as WordPress ship quality code on a schedule.

Guest Goerge Stocker cuts through the often polarizing debate about Test-Driven Development (TDD) and offers his view on when the practice does and DOES NOT make sense, based on technology as well as human factors which are often overlooked.  We discuss the concept that TDD is one of a vast array of techniques to choose from, and some of what goes into selecting the right tool for the job.ResourcesBoundaries talk by Gary Bernhardt of Destroy All SoftwareIs TDD Right for Your Team? by George StockerToday's GuestGeorge Stockerhttps://georgestocker.comTwitter: @gortokWatch this episode on YouTube.

In this episode, I was joined by Ian Cooper to chat about Test Driven Development (TDD)! We discussed pain points that a lot of people hit when attempting to do TDD, and how to avoid them.For a full list of show links, see the website here

What if we thought about our conversations like a unit test in Test Driven Development (TDD). Not in the sense of treating people like computers and being robotic but in the sense of failing fast and correcting fast... in the sense of having a test in place to verify understanding and context before taking the next small step in the conversation. Would we avoid big batch conversations full of misunderstandings? Would we catch errors in conversation before they compound into production defects? Join Chris and Austin as they discuss with Mark Holmes about "TDD for people" as well as micro-retrospectives and experimentation. Video and show notes: https://youtu.be/BexHm0TD6gM 

En esta interesante charla, Jorge Turrado nos cuenta sus experiencias y nos aclara muchos conceptos sobre el testing de aplicaciones, integración continua, Test Driven Development (TDD), y cantidad de cosas más. El curso de testing de Jorge en campusMVP Enlaces mencionados en la conversación: La muerte de la locura de los microservicios: https://www.campusmvp.es/recursos/post/la-muerte-de-la-locura-de-los-microservicios-en-2018.aspx Report Generator: https://github.com/danielpalme/ReportGenerator --- Send in a voice message: https://anchor.fm/campusmvp/message

In this episode I talk with Hamish Tedeschi, CEO and Founder at Mechanical Rock. Mechanical Rock's mission is to deliver better software, faster while helping clients transform the way they deliver. Their methodology is based on DevOps, modern code-driven infrastructure and test first development. DevOps is what they do. Hamish and I talk about what DevOps really is all about and how he saw a space in the market around modern application development focused on public cloud platforms and a do everything as code mantra! Their DevOps philosophy delivers better software, faster through Everything-as-Code under configuration management, including immutable infrastructure validated via Behaviour Driven Infrastructure (BDI), Test First Development, exemplified by Test Driven Development (TDD) and Behaviour Driven Development (BDD), Continuous Build via deployment pipelines, including automated testing at the unit and scenario level, Continuous Operations including monitoring and alerting, auto remediation and optimisation and Transparency of information, and active collaboration across teams, throughout the process Mechanical Rock was founded in 2014 with the company headquartered in the Perth, Western Australia Technology and Technology Partners Mentioned AWS, GCP, Azure, Microsoft, CNCF, Snowflake, HashiCorp, Terraform Shout Outs and Notes Web: https://www.mechanicalrock.io GitHub: https://github.com/mechanicalrock DevOps Dream Game: http://devops.games Latency Conference: https://www.latencyconf.io YouTube: https://www.youtube.com/channel/UCJyuSH1MDXDWwSR-7s6UL3Q Interested in being on #GTwGT? https://launch.gtwgt.com Music: https://www.bensound.com

An introduction to Test Driven Development (TDD) and how to make the best use of it in your software project with our experts on this podcast from 99x. Host: Saiyaff Farook, Senior Software Engineer @ 99x Speakers: Rahunath Yoganathan, Software Engineer @ 99x Thank you for tuning in. Follow our channel for new tech-related podcasts every Thursday!

Originally published August 28, 2019 Kent Beck is a legendary figure in the world of software engineering.  Kent was an early advocate of Test-Driven Development (TDD), and popularized the idea of writing unit tests before writing code that would satisfy those unit tests. A unit test isolates and tests a small piece of functionality within The post Facebook Engineering Process with Kent Beck (Repeat) appeared first on Software Engineering Daily.

Originally published August 28, 2019 Kent Beck is a legendary figure in the world of software engineering.  Kent was an early advocate of Test-Driven Development (TDD), and popularized the idea of writing unit tests before writing code that would satisfy those unit tests. A unit test isolates and tests a small piece of functionality within The post Facebook Engineering Process with Kent Beck (Repeat) appeared first on Software Engineering Daily.

Originally published August 28, 2019Kent Beck is a legendary figure in the world of software engineering. Kent was an early advocate of Test-Driven Development (TDD), and popularized the idea of writing unit tests before writing code that would satisfy those unit tests. A unit test isolates and tests a small piece of functionality within a large piece of software. Practitioners of Test-Driven Development write tens or hundreds of tests in order to cover a large variety of cases that could potentially occur within their software.When Kent Beck joined Facebook in 2011, he was 50 years old and thought he had seen everything in the software industry. During Facebook Boot Camp, Kent started to realize that Facebook was very different than any other company he had seen. Facebook Boot Camp is the six-week onboarding process that every new hire learns about the software practices of the company.After graduating Facebook Boot Camp, Kent began to explore Facebook's codebase and culture. He found himself rethinking many of the tenets of software engineering that he had previously thought were immutable.Kent joins the show to discuss his time at Facebook, and how the company's approach to building and scaling products thoroughly reshaped his beliefs about software engineering.

Originally published August 28, 2019 Kent Beck is a legendary figure in the world of software engineering.  Kent was an early advocate of Test-Driven Development (TDD), and popularized the idea of writing unit tests before writing code that would satisfy those unit tests. A unit test isolates and tests a small piece of functionality within The post Facebook Engineering Process with Kent Beck (Repeat) appeared first on Software Engineering Daily.

Test Driven Development is the practice of writing your tests to explore how your code should be structured and to verify its functionality. Bob and Chuck explore the various thoughts around how to write tests, what to test, and how testing will save you time and effort in the long run. Then, they dive into how writing tests first through Test Driven Development (TDD). This episode walks you through starting with Test Driven Development (TDD) and how Test Driven Development can help improve your development practices. Check Out Bob's Advanced TDD Course on Clean Coders

Resources Mentioned in this episodeIntroduction to Test Driven Development (TDD).TDD Vs BDD – Analyze The Differences With Examples.Test Driven Development: By Example.Messenger Platform Tutorial (TDD Approach).https://cucumber.io/Example Mentioned in the Episode:Title: Returns and exchanges go to inventory.As a store owner,I want to add items back to inventory when they are returned or exchanged,so that I can track inventory. Scenario 1: Items returned for refund should be added to inventory.Given that a customer previously bought a black sweater from meand I have three black sweaters in inventory,when they return the black sweater for a refund,then I should have four black sweaters in inventory. Scenario 2: Exchanged items should be returned to inventory.Given that a customer previously bought a blue garment from meand I have two blue garments in inventoryand three black garments in inventory,when they exchange the blue garment for a black garment,then I should have three blue garments in inventoryand two black garments in inventory. Episode Picks:Luay:  Facebook Engineering Process with Kent Beck. 

Kent Beck is an American software engineer, writer and thought leader. He has been, and remains, one of the most influential figures in the field of software development over the past 20 years. He is best known as the creator of the eXtreme Programming (XP) software development methodology and proponent of Test Driven Development (TDD). In 2001 he was one of 17 signatories of the Agile Manifesto that started a movement which revolutionised the world of software development around the world. He first visited South Africa in 2005 as a guest of the JCSE. This initiated a long association between Kent and the software engineering community of South Africa and Africa. In this episode Kent is in discussion with Prof Barry and his co-host Kerryn Gammie. If life is a relay race, what is the baton he will hand over to Kerryn and her generation of Africa's future digital leaders.

Kent Beck is an American software engineer, writer and thought leader. He has been, and remains, one of the most influential figures in the field of software development over the past 20 years. He is best known as the creator of the eXtreme Programming (XP) software development methodology and proponent of Test Driven Development (TDD). In 2001 he was one of 17 signatories of the Agile Manifesto that started a movement which revolutionised the world of software development around the world. He first visited South Africa in 2005 as a guest of the JCSE. This initiated a long association between Kent and the software engineering community of South Africa and Africa. In this episode Kent is in discussion with Prof Barry and his co-host Kerryn Gammie. If life is a relay race, what is the baton he will hand over to Kerryn and her generation of Africa’s future digital leaders.

5am Mester Scrum Show #357 Live - Daily Scrum is Not Always the Answer and Using Bug Fixing to learn TDD - Today's topics:  (1) Many beginning Scrum Masters and even Agile Coaches make the mistake on insisting on Daily Scrum, but you need 2 Things and (2)  Team Resistant to Test Driven Development (TDD) well use Bug Fixing to learn hands on .  Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing.  #5amMesterScrum #scrum #agile #business #scrummaster #agilecoach #coaching #TDD #testing #test #dailyscrum #dsu #bugs #defects #standup  5am Mester Scrum Show #357 went live on Youtube at 732am EST Tuesday 7/14/2020 .   Happy Scrumming, Social Media Roll Call   LinkedIn: https://www.linkedin.com/company/5ammesterscrum/ Youtube: https://www.youtube.com/c/5ammesterscrum Facebook: https://www.facebook.com/5ammesterscrum/ Instagram: https://www.instagram.com/5ammesterscrum/ Twitter: https://twitter.com/5amMesterScrum/ TikTok: (search 5amMesterScrum)  Podcasts: (search 5amMesterScrum) Spotify, Google Music Player, PodBean, iTunes, Stitcher, PlayerFM, Breaker 

This podcast is all about Test-Driven Development (TDD). TDD can significantly increase productivity and software quality, eliminate regressions, and contribute to developer happiness.

Links:Hashnode – the developer communitySyed Fazle Rahman, Sandeep’s co-founderHashnode’s tech stackRemote – book from BasecampAccel – the venture capital (VC) firmAI Superpowers – Book on how China uses AIHighlights and overview for you:The first 30 minutes: the entrepreneurial journeyStarting from 26:00: we talk about the development processesHow and why Sandeep started his developer community (1:00)How he met the investor firm Accel and asked for funding (5:54)How he seeded and kickstarted the community (11:27)How they spend time building a different pivot system – blockchain-based community (14:43)How focusing on the wrong things led them down the wrong path. The friendly community wasn’t existent anymore. (21:15)Sandeep explains what it means to be working with a VC firm (23:17)Does Sandeep feel like an expert for software development? (26:09)Sandeep’s experience with Next.js and MERN (Mongo, Express, React, Node) tools? (27:05)How does their development process look like? (28:55)How do they check for site reliability and security issues? (32:14)Do they run static analysis tools? Do they measure test coverage? Which testing practice do they follow? (33:48)Why do they run a remote company? (38:29)What about their DevOps process? Who has access to the production server, and how does deployment work? (42:13)How do they deal with technical debt? (44:27)Which books is Sandeep reading currently? (49:18) All questions by McKayla:Sandeep, you’re running a developer community, are you a developer yourself? (0:50)So how did you become a developer? What was your way? Are you a self-taught developer or did you go to university? (1:00)Did you have the urge to start your own company already during University or did it just come later? (1:45)And, what was your first-day job after college? (2:40)And when you started Hashnode, did you do that full-time immediately, or was that as a side project again, so in addition to your nine to five job? (3:11)So how did you decide which technologies to use? How Hashnode, you know, this community should look like? And how did the whole process start? (3:45)And did you choose that tech stack because you wanted to make progress really fast and because you knew those technologies very well from your previous jobs and side projects you built while at university? (5:07)How did you validate the idea of Hashnode? (5:54)Can you tell me a little bit more about Accel, the VC firm? (7:18)Was Accel the first firm that you ask for money and pitched your idea, or did you also try somewhere else? (7:46)Was it sort of a smooth ride after talking to Accel or have there been ups and downs before you actually got they funding? (8:30)After you pitch your idea, do you just wait or ping them multiple times? (9:27)Do you have an idea of how many people used DevMag after the Producthunt launch? (10:50)How did you know to kickstart the community from scratch? (11:27)So your focus was really on building the community and not the system anymore, right? (12:49)Was your first hire a community manager? (13:33)How did you find your first employees? (14:09)Are the same people still at your company or have you had to turn in your employees? (14:36)What is a blockchain community? (15:42)Why did this idea fall apart? (16:27)OK so that’s actually another sort of pivot of your company, right? From this Q&A style website to blogging functionality for developers. So how is that going? (17:47)Did you raise money for that as well? (19:09)What’s your vision for this Devblog? What should be the end result? (19:18)And for some of the monetization strategies that you brainstorm is there the blockchain coming back? (19:42)With all those pivots, have you still been able to keep this 70-30% split between development and community management? (20:06)And in these six months that you stopped attending so much to the community what happened? (21:19)Does the venture capital (VC) firm give you some feedback on big decisions? (23:17)Do you have to ask the VC firm for permissions for big changes that you want to make? (24:16)Does the VC firm also have opinions about the software development side of the project for example best practices you should follow or which technologies you should use? (25:17)Do you feel like an expert for software development? (25:57)Which technical decisions were really good decisions? (27:05)How much of the codebase was really rewritten? (27:56)So how does your development process in general look like do you do testing or code reviews? (28:53)And so, there’s at least one person that has to look through the code review? (30:41)And it doesn’t matter who that is? So, if that person says that it looks fine to me than you can actually push it to production? (30:45)If they push it to production and there are any bugs how would they revert it? (31:11)How can a user report a problem? (31:41)How do you address site reliability issues and security related issues? (32:14)Something else I wanted to talk a little bit more about is testing. Do you follow some testing methodology, like test-driven development or is that up to everybody on the team to decide? (33:48)Do you do Test Driven Development (TDD)? (34:19)And do you have something like code coverage to know if you’re covered enough of the code? Do you use metrics like that? (35:31)Do you use other static analysis tools? (36:27)And why did you stop using static analysis tools? (36:44)So, is this your way of reducing the overhead while you just figuring out the features and what the product will look like? (37:57)So, a little bit before you told me about the offices that you actually got an office with the VC funding, but that you are remote. What’s the story behind that? (38:29)And why did you decide to go from being two people in an office to hiring all over the world and working remotely? (39:41)Did you adjust the way you work or the tools for remote development? (40:48)And have you ever met your two European employees already? (41:46)So especially remote work is really built upon trust. So as I can imagine at the beginning you have to put a lot of trust forward, how was that for you? (42:13)So, one of the other things I wanted to talk to you about is your DevOps and your deployment strategy. Has everybody access and the right to deploy to the production or is there some specific process you follow? (42:54)Do you have a specific time that you deploy to production? (43:50)How do you deal with technical debt? (44:27)Do you have rules or processes or tools that help you not to introduce new technical depth? (45:24)So you say you’re having no hard deadlines. Would you describe your way of working sort of an agile way working? (46:21)So, if you would hire now let’s say, two other people, what would their roles be? (47:25)What’s the key metrics that you think help you go in the right direction? (47:52)Is there some budget that people can spend like on books or conferences to learn? (48:34)What are the books you are looking forward to reading? (49:18)Do you have some ideas on how AI can bring your developer community to the next level? (49:42)

Kent Beck is a legendary figure in the world of software engineering.  Kent was an early advocate of Test-Driven Development (TDD), and popularized the idea of writing unit tests before writing code that would satisfy those unit tests. A unit test isolates and tests a small piece of functionality within a large piece of software. The post Facebook Engineering Process with Kent Beck appeared first on Software Engineering Daily.

Following up on our earlier mass-storage support announcement for TinyUSB, we just added WebUSB support! You can now send and receive data over Chrome (or other WebUSB) browsers with Javascript or whatever else is your favorite web programming language. This can make for really interesting interactions where people don't need any drivers or software to send/receive commands, or perhaps to expose some sort of REPL. The example code is here: https://github.com/hathach/tinyusb/blob/master/examples/device/webusb_serial/src/main.c and here's what the webpage code looks like: https://github.com/adafruit/Adafruit_TinyUSB_Arduino/tree/master/docs/examples/webusb-serial We'll be adding this to our Arduino library shortly, and will follow up when we have the library committed and updated tinyUSB currently supports SAMD21, SAMD51, nRF52840, various LPCs, and STM32F4 - more chips will be supported soon! tinyusb is an open-source (BSD-licensed) USB Host/Device/OTG stack for embedded micro-controllers, especially ARM MCUs. It is designed to be user-friendly in term of configuration and out-of-the-box running experience. #usb #tinyusb #webusb In addition to running without an RTOS, tinyusb is an OS-awared stack that can run across RTOS vendors. For the purpose of eliminating bugs as soon as possible, the stack is developed using Test-Driven Development (TDD) approach. More documents and API reference can be found at http://docs.tinyusb.org https://www.tinyusb.org Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Adafruit on Instagram: https://www.instagram.com/adafruit Subscribe to Adafruit on YouTube: http://adafru.it/subscribe Join our weekly Show & Tell on G+ Hangouts On Air: http://adafru.it/showtell New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

Gregg and Adam discuss implementing the builder pattern in Vue.js, Accessible Form Validation Messages with ARIA and Vue.js, GraphQL course for Vue developers by Hasura.io, VueJS Functional Calendar, Test Driven Development (TDD), and tips on Unit Testing Vue Components with Jest

In this episode, Chuck talks about test-driven development (TDD). He talks about the practice, and ways agile coaches and scrum masters can help their teams adopt it. This is an episode in a series of tricky topics for agile coaches to teach.Support the show (https://www.patreon.com/agilechuckwagon)

We started this episode discussing about readability of code. What actually is readability? It seems, that next to names, there are other important things to consider, like visual structure. In the second part we talked about how to get started with Test Driven Development (TDD) in a project were nobody else is doing it. We found a few suitable ways to get things started. Finally we concluded the episode with our personal history, how we each one of us got started with TDD.

Bu hafta konuğumuz OpsGenie'den Ömer Özkan ile Test Driven Development(TDD) nedir ve neden önemlidir sorularını cevaplamaya çalıştık. Ömer verdiği örnekler ile yazılımda test yazmanın önemi, TDD'nin yani test güdümlü yazılım geliştirmenin ne demek olduğu ve çevik yazılım geliştirmedeki yerini anlattı. OpsGenie'den de örnekler verdiğimiz bölümde umarım, özellikle yöneticilere, bu gibi temiz kod yazmamıza yardımcı yazılım geliştirme pratiklerinin ürününüzün en büyük avantajlarından olabileceğini anlatabilmişizdir. Konuk - Ömer Özkan https://www.linkedin.com/in/omerozkan/ https://twitter.com/OmerOzkan_ Host - Serhat Can @srhtcn

Test-Driven Development (TDD) é uma prática de desenvolvimento e um pré-requisito para Continuous Delivery. Felipe Martins (UPX) e Nelson Senna (TopTal) explicam porquê praticar TDD, os diferentes tipos de testes existentes e como começar a praticar TDD. Referências e mais detalhes em: https://www.10deploys.com/episodios/010-test-driven-development

Some people have very strong coding instincts. They can solve problems just by looking at them, and feel like rockstars. But being a rockstar coder can only get you so far. You need one other crucial element: discipline. In this podcast, Bill shares his disciplined approach to writing code and to work in general. Written by Bill Sourour: http://twitter.com/billsourour Read by Abbey Rennemeyer: http://twitter.com/abbeyrenn Original article: https://fcc.im/2IzwWdH Learn to code for free at: https://www.freecodecamp.org Intro music by Vangough: https://fcc.im/2APOG02 Transcript: I wrote my first few lines of code almost 32 years ago, when I was 6 years old. I developed very strong coding instincts. I could look at any problem and immediately know how to solve it, just by intuition. By the time I started coding the web for a living, I felt like a rock star. I found and fixed bugs faster than any of my co-workers. My team started assigning me all the most challenging features and the most nagging bugs. They even started calling me a “wizard.” But following your intuition can only take you so far. I hit a plateau. And no amount of coding instinct was going to push me past it. The trouble with trusting your gut Unfortunately, intuition as a technique for learning and problem solving doesn’t scale very well. When you rely on instinct and intuition alone, you get a curve that looks like this (See original article for graph). Of course, you can choose to accept your limits and only ever deal with problems below the line. This will indulge your “rock star coder” fantasy, but it will quickly begin to limit your growth and your career. Plus, it’s boring. As I pushed myself further and further ahead in my career — and started to really challenge my own abilities — I began to notice a disturbing trend. I was no longer the fastest kid on the block. I had always known that I’d eventually run into people smarter and more talented than me. (My delusions of grandeur were still grounded in reality. I’m no genius.) But when I looked around, I realized that some of the people beating me were not using a superior intellect or some sort of innate gift for code. They just had a secret weapon that I sorely lacked: discipline. It turns out that a consistent, repeatable, methodical approach to learning and problem solving will eventually outperform any natural gifts — or instincts — that you may have developed. Let’s tool up those problem solving abilities Regardless of who you are, how much passion or natural talent you have, you will eventually hit a hard ceiling. I’m going to share with you a few techniques that will dramatically improve your disciplined problem solving abilities. I’m assuming that, if you have a debugger, you’ve already run it, Googled the output, and had no luck. I’m also assuming that if the problem was reported by someone else, you have been able to reproduce the problem. This second assumption is a big one. If you can’t reproduce the problem, then that needs to be your first step. You need to compare the context and environment in which the problem occurred to the context and environment in which you are trying to reproduce it. Start eliminating any differences you can, one by one, until you can reproduce. Once you can reproduce the problem, and after the debugger has failed to be of any use, you can try the following disciplined approaches. RTFM Read the documentation, you fool! (Admittedly this isn’t what RTFM stands for exactly, but there may be children reading.) Actually read it — more than once if you need to. Don’t just skim it looking for something you can copy, paste, and pray will work. The problem is you want an answer fast. You want that thrill of victory. But you’re not willing to put in the work. So slow down. Take a breath. Grab a coffee. And read the relevant documentation all the way through. If you have no documentation, consider creating some, then sharing it with others after you’ve fixed the problem. Test Your Assumptions If you expect something to work and it doesn’t, it’s because you’ve made a bad assumption somewhere along the way. Take an inventory of your assumptions and try to prove that each one is true. Start with the most basic assumptions that can be quickly tested. Is the server actually running? Is it connected to the network? Is everything spelled correctly? Are all the brackets and semicolons in the right place? If you don’t start with the simple things, and it does turn out to be one of these things, when you finally figure it out you will want to jump out a window. So save yourself the headache. Disassemble and Reassemble Remove components from the solution until it starts working again, then put the components back one-by-one in order to find the broken piece. This feels tedious and scary, but it is one of the most effective, disciplined ways to find the cause of a bug in your code. Make sure you have a backup before you start though, in case you accidentally end up with Humpty Dumpty code (code that you can’t put back together again). By the way, if you find yourself in a situation where you don’t know how to reassemble the code back to how it was, this is an indication of a potentially bigger problem: you don’t understand the codebase you’re working with. That’s bad bananas, my friend. If you’re on a tight deadline, seek help immediately from someone who understands the codebase better than you. If no such person exists, dig in for a long night, and prioritize getting to know and understand how this code works, so that you can fix it. Eliminate Variables Anything that can change from one trial to the next should be made to remain static while you’re debugging. You can’t hit a moving target. This is where Test Driven Development (TDD) comes in handy. If you’re using TDD, then you should have some mock objects at your disposal. Mock objects are simulated objects that mimic the behavior of real objects in controlled ways. A programmer typically creates a mock object to test the behavior of some other object, in much the same way that a car designer uses a crash test dummy to simulate the dynamic behavior of a human in vehicle impacts. — Wikipedia If you didn’t do TDD, then you’ll need to mock out any moving parts now, so that you can find the bug under stable conditions. Here’s a tip: if you mock an object and the bug suddenly goes away, then the bug is likely in the object you mocked. Use the “Saff Squeeze” There’s a technique called the “Saff Squeeze” — named and popularized by Kent Beck — that is sort of a cross between the two ideas above. He describes it this way: “To effectively isolate a defect, start with a system-level test and progressively inline and prune until you have the smallest possible test that demonstrates the defect.” — Kent Beck So instead of formal mocks or code disassembly, you simply add the body of the functions that you’re testing into the test itself, then move the assertions down until the bug goes away. This has the added benefit of leaving you with smaller, more specific tests. Edit: Thanks to Jim Balter for pointing out this link to a good example and explanation of the Saff Squeeze. After You Fix It, Break It and Fix It Again Never leave a bug until you fully understand how you fixed it. You should be able to reproduce the bug and fix it again at will. I can’t stress this enough. If you fix a bug and you’re not sure exactly what caused it or how you managed to fix it, that bug will come back to bite you at the worst possible time. What About Those Instincts? Now that you’ve learned these techniques, does that mean you should always use them first instead of relying on your instincts? No. Absolutely not. What I recommend is that you give your instincts a time box in which to succeed. If you have a strong hunch about what the problem might be — and you can test your hunch quickly — do that first. If the bug is below the green line in the chart above, chances are that your instincts will be the fastest path to a solution. Once you’ve quickly tried your first or second hunch and been wrong though, stop the shotgun approach and start doing things methodically. Having both instincts and discipline will make you one of the top coders on any team. To help you even more, I have put together a free PDF list of my five favourite code refactoring techniques — that lead to fewer bugs — get it by clicking the link in the original article.

Test Driven Development (TDD), good idea in theory, but in practice? Carl and Richard talk to John Callaway and Clayton Hunt about their success with TDD. At it's simplest level, TDD is about writing tests first, before coding. In practice, everything is more complicated than that. Writing testable code isn't as simple as it seems, and refactoring existing code to become testable can cause it to break - which is why you wanted tests in the first place. John and Clayton talk through their experiences getting things right and exploring the advantages that TDD brings - more reliable software that sustains for longer and can continue to evolve!Support this podcast at — https://redcircle.com/net-rocks/donations

Test Driven Development (TDD), good idea in theory, but in practice? Carl and Richard talk to John Callaway and Clayton Hunt about their success with TDD. At it's simplest level, TDD is about writing tests first, before coding. In practice, everything is more complicated than that. Writing testable code isn't as simple as it seems, and refactoring existing code to become testable can cause it to break - which is why you wanted tests in the first place. John and Clayton talk through their experiences getting things right and exploring the advantages that TDD brings - more reliable software that sustains for longer and can continue to evolve!Support this podcast at — https://redcircle.com/net-rocks/donations

01:41 – Dan’s Superpower: Optimization 03:26 – Are “Improve” and “Optimize” the same thing? Kaizen (https://en.wikipedia.org/wiki/Kaizen) Kaikaku (https://en.wikipedia.org/wiki/Kaikaku) Cost Accounting (https://en.wikipedia.org/wiki/Cost_accounting) 17:20 – How is cost accounting affected by demographics and privilege? 33:34 – Team Alignment, Collectiveness, and Camaraderie 37:42 – Behavior-Driven Development (BDD) (https://en.wikipedia.org/wiki/Behavior-driven_development) vs Test-Driven Development (TDD) (https://en.wikipedia.org/wiki/Test-driven_development) Write the executable specifications to guide development. Then, delete most of them to optimize for documentation. Don’t pretend that the code is tested; that’s quite different. from @tastapod (https://twitter.com/tastapod?ref_src=twsrc%5Etfw) on @greaterthancode (https://twitter.com/greaterthancode?ref_src=twsrc%5Etfw) — Jessica Kerr (@jessitron) March 14, 2018 (https://twitter.com/jessitron/status/973987032094728192?ref_src=twsrc%5Etfw) 58:00 – Customer Empathy Growing Object-Oriented Software, Guided by Tests (https://www.amazon.com/gp/product/0321503627/ref=as_li_qf_asin_il_tl?ie=UTF8&tag=therubyrep-20&creative=9325&linkCode=as2&creativeASIN=0321503627&linkId=4a035427b40d7639d3ce1d4431eb7c49) Reflections: Jessica: Meeting a customer need = congressive. Dan: Collaboration is how you get work done. Jamey: Replacing “responsibility” with “duty of care”. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guest: Dan North.

An in depth discussion of Test Driven Development (TDD) should include a discussion of Test First. So that's where we start. Why write tests first? How do you know what tests to write? What are the steps for test first? Isn't this just TDD? Functional Tests vs Unit Tests

Test-Driven Development (TDD) has been so successful that it's now unfashionable. We seem to have lost the excitement and empowerment we felt when we first stumbled onto TDD a dozen years ago. Now it's just a chore that only bothers developers. Were we fooling ourselves, or did the message get confused along the way? In this talk, I will revisit the basics, the essence of what makes TDD work. I will look at some of the common difficulties that I see with teams that are struggling. I will show how TDD is as much an approach to development as a programming technique and how, like BDD, it's not about testing.

Eine Einführung in Test Driven Development (TDD) gibt es in der einhundertdritten Folge des Anwendungsentwickler-Podcasts. Inhalt Was ist Test Driven Development (TDD)? Beim TDD werden die Tests vor dem Produktivcode geschrieben. Wie läuft der TDD-Zyklus ab? Red, green, refactor. Der Test muss fehlschlagen, dann wird er so einfach wie möglich grün gemacht, dann wird refaktorisiert.... Der Beitrag Einführung in Test Driven Development – Anwendungsentwickler-Podcast #103 erschien zuerst auf IT-Berufe-Podcast.

Episode 004: Testing Summary Sam Phippen, Justin Searls, and Noel Rappin spend this episode talking about the value of test-driven development (TDD) as well as its cost. They discuss the kinds of problems that developers are likely to have after they learn TDD and attempt to apply it to a large application. Learn why Rails is both great and terrible for automated testing, and how testing can influence the structure of your code. Guests Sam Phippen (https://twitter.com/samphippen): Engineer at Digital Ocean (https://www.digitalocean.com/) and member of the RSpec (https://github.com/rspec) Core Team Justin Searls (https://twitter.com/searls): Writes bad code effortlessly and cofounder of Test Double (http://testdouble.com/). Maintainer of several testing tools, and frequent speaker on test related topics. Show Notes 01:30 - Intermediate Level Problems in Testing 04:58 - The Value of Testing Boundaries by Gary Bernhardt (https://www.youtube.com/watch?v=yTkzNHF6rMs) 15:15 - Isolated Unit Tests 17:52 - Structuring Applications 23:13 - Test-Driven Development (TDD) (https://en.wikipedia.org/wiki/Test-driven_development) Growing Object-Oriented Software, Guided by Tests (https://www.amazon.com/Growing-Object-Oriented-Software-Guided-Tests/dp/0321503627) 33:22 - TDD in a Smalltalk (https://en.wikipedia.org/wiki/Smalltalk) Environment 35:00 - Isolating Tests in a Rails Environment Rake Without Rails (http://blog.testdouble.com/posts/2016-12-15-rake-without-rails.html) 36:54 - Test Tools minitest (https://github.com/seattlerb/minitest) Dan North: Introducing BDD (https://dannorth.net/introducing-bdd/) teenytest (https://github.com/testdouble/teenytest) RSpec (https://github.com/rspec) Tips & Resources: Sam: Sandi Metz: The Magic Tricks of Testing @ Rails Conf 2013 (https://www.youtube.com/watch?v=URSWYvyc42M) Test Smells (https://github.com/testdouble/test-smells#test-smells) Justin Searls: How to Stop Hating Your Test Suite @ RubyConf 2015 (https://www.youtube.com/watch?v=VD51AkG8EZw) Justin: Find some little problem and instead of implementing it in a Rails app, type bundle.gem and then make up a name and then practice and invent your own way of organizing code and tests so you can break things down. Noel: JUnit Test Infected: Programmers Love Writing Tests (http://junit.sourceforge.net/doc/testinfected/testing.htm) As you’re trying to test stuff, really try to focus on going back and forth between the tests and the code more rapidly than you’re probably doing so right now. Special Guests: Justin Searls and Penelope Phippen.

This principle is much like the one previous about sustainable development. Agile doesn't ask us to shortcut quality and increase technical debt in an effort to deliver software faster. It is precisely because we do not shortcut quality and incur technical debt that we are able to move faster. I have worked with many teams to introduce Behavior Driven Development (BDD) because, among a great number of other advantages, BDD allows developers an easier way to access the practice of Test Driven Development (TDD). And, in my experience, TDD is the only way I have seen out of the practice of “Big Up Front Design”.

The Software Process and Measurement Cast 406 features our interview with Erik van Veenendaal.  We discussed Agile testing, risk and testing, the Test Maturity Model Integrated (TMMi), and why in an Agile world quality and testing still matter. Erik van Veenendaal (www.erikvanveenendaal.nl) is a leading international consultant and trainer, and a recognized expert in the area of software testing and requirement engineering. He is the author of a number of books and papers within the profession, one of the core developers of the TMap testing methodology, a participant in working parties of the International Requirements Engineering Board (IREB). He is one of the founding members of the TMMi Foundation, the lead developer of the TMMi model and currently a member of the TMMi executive committee. Erik is a frequent keynote and tutorial speaker at international testing and quality conferences. For his major contribution to the field of testing, Erik received the European Testing Excellence Award (2007) and the ISTQB International Testing Excellence Award (2015). You can follow Erik on twitter via @ErikvVeenendaal. Re-Read Saturday News This week we continue our re-read of Kent Beck’s XP Explained, Second Edition with a discussion of Chapters 14 and 15.  This week we dive into design and scaling. These chapters  address two critical and controversial topics that XP profoundly rethought. I am still collecting thoughts on what to read next. Is it time to start thinking about what is next: a re-read or a new read?  Thoughts? Use the link to XP Explained in the show notes when you buy your copy to read along to support both the blog and podcast. Visit the Software Process and Measurement Blog (www.tcagley.wordpress.com) to catch up on past installments of Re-Read Saturday. Next SPaMCAST The next Software Process and Measurement Cast will focus on our recent revisit of Test Driven Development (TDD).  TDD is an important feature of XP that can be (and should be) used if quality and efficiency are important to your organization. We will also have a new column from Steve Tendon (welcome back Steve!)  and Gene Hughson AND maybe one more but we will see!    Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book here. Available in English and Chinese.

Test-Driven Development (TDD) is a mature methodology now, right? So how do you get it right? Carl and Richard talk to Justin Searls about his experiences helping teams implement TDD. As Justin says, TDD is just a tool in the toolbox for making long-lived software. In its maturity, different flavors of TDD have emerged, and Justin digs into the Detroit or Classical TDD versus the London TDD. It's all about testing, but with some style variations. How do you keep your tests resilient as software evolves? Justin talks about the right amount of abstraction and organizing a hierarchy of tests so that you can manage change effectively. TDD works!Support this podcast at — https://redcircle.com/net-rocks/donations

Test-Driven Development (TDD) is a mature methodology now, right? So how do you get it right? Carl and Richard talk to Justin Searls about his experiences helping teams implement TDD. As Justin says, TDD is just a tool in the toolbox for making long-lived software. In its maturity, different flavors of TDD have emerged, and Justin digs into the Detroit or Classical TDD versus the London TDD. It's all about testing, but with some style variations. How do you keep your tests resilient as software evolves? Justin talks about the right amount of abstraction and organizing a hierarchy of tests so that you can manage change effectively. TDD works!Support this podcast at — https://redcircle.com/net-rocks/donations

01:21 - John Reid Introduction Twitter GitHub Blog 02:45 - Tools For Testing and Test-Driven Development (TDD) XCTest OCHamcrest OCMockito 03:24 - Matching/Matchers 07:13 - Getting Started OCHamcrest/README 08:58 - Partial Matching 10:26 - Mocking and Stubbing 14:04 - TDD Process and Workflow 17:49 - TDD vs Unit Testing Red, Green, Refactor 19:54 - iOS Code That Doesn’t/Does Adapt Well to TDD 21:17 - User Interface Testing 24:58 - End-to-End Testing 30:18 - Communication and Collaboration Working Effectively with Legacy Code by Michael Feathers 33:39 - OCMock, OCMockito 39:13 - OCMockito with Swift? Quick Brian Gesak 41:07 - Inside Out vs Outside In Picks wit.ai (Mike) Jon's UIViewController TDD Screencast (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) NeewerHandheld Video Stabilizer for DV GoPro Mini Cameras (Chuck) Cell Phone Tripod Adapter (Chuck) Working Effectively with Legacy Code by Michael Feathers (Jon) Clean Coders (Jon) AppCode (Jon)

01:21 - John Reid Introduction Twitter GitHub Blog 02:45 - Tools For Testing and Test-Driven Development (TDD) XCTest OCHamcrest OCMockito 03:24 - Matching/Matchers 07:13 - Getting Started OCHamcrest/README 08:58 - Partial Matching 10:26 - Mocking and Stubbing 14:04 - TDD Process and Workflow 17:49 - TDD vs Unit Testing Red, Green, Refactor 19:54 - iOS Code That Doesn’t/Does Adapt Well to TDD 21:17 - User Interface Testing 24:58 - End-to-End Testing 30:18 - Communication and Collaboration Working Effectively with Legacy Code by Michael Feathers 33:39 - OCMock, OCMockito 39:13 - OCMockito with Swift? Quick Brian Gesak 41:07 - Inside Out vs Outside In Picks wit.ai (Mike) Jon's UIViewController TDD Screencast (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) NeewerHandheld Video Stabilizer for DV GoPro Mini Cameras (Chuck) Cell Phone Tripod Adapter (Chuck) Working Effectively with Legacy Code by Michael Feathers (Jon) Clean Coders (Jon) AppCode (Jon)

Kito and Daniel are joined by special guest Seb Rose (co-author of The Cucumber for Java Book: Behaviour-Driven Development for Testers and Developers). They discuss new releases from Polymer, ICEfaces, PrimeFaces,  JBoss EAP, SonarCube, Pitest, IntelliJ IDEA, Serenity, and more. They also discuss Behavior-driven-testing (BDD), Cucumber, Geb, Spock, and Test-Driven Development (TDD). UI Tier AngularFaces 2.1.3 has been released! Polymer 0.8 Release ICEfaces EE 4.0.0.GA   Includes ICEfaces Mobile Device Simulator ICEpdf 5.1.2: Now With Enhanced Asian Font Capabilities PrimeFaces Sentinel 1.2 Released PrimeFaces 5.2.RC1 Released Introducing PrimeFaces Spark Services (Middleware & Microservices) Tier JBossWS 5.0.0.Final is available! JBoss EAP 6.4 now available Mobile AeroGear iOS SDK v2.3 is out! Misc SonarQube 5.1 released  - http://www.sonarqube.org/sonarqube-5-1-in-screenshots/ Pitest 1.1.5 released  - http://pitest.org Sonar Pitest Plugin 0.5 released  - https://github.com/SonarCommunity/sonar-pitest JOSRA Git Automated Branching Strategy & Jenkins Plugin  - http://www.josra.org/blog/An-automated-git-branching-strategy.html IntelliJ IDEA 14.1 released  - decompiler with extended debugging facilities Gherkin 3 development continues  - https://groups.google.com/forum/#!msg/cukes/YLKsqbBMBoI/DYhfFx8GBegJ Serenity 1.0.47 released  better Cucumber integration - http://thucydides.info/docs/serenity-staging/ Discussion Testing with Cucumber and comparison to Geb and Spock - [Cucumber is a collaboration tool - https://cukes.info/blog/2014/03/03/the-worlds-most-misunderstood-collaboration-tool] Teaching TDD with CyberDojo - http://cyber-dojo.org What’s coverage good for? A. Killing mutants efficiently. Events Javazone, Oslo - September 9-10, 2015 No Fluff Just Stuff Dallas May 29 - 31, 2015 Salt Lake City June 5 - 6, 2015 Gradle Summit June 11 - 12, 2015 Austin July 10 - 12, 2015 ÜberConf July 21 - 24, 2015 Other Claysnow Limited (Seb Rose’s company) To TDD or not to TDD? That is not the question. Liz Keogh’s blog Growing Object-Oriented Software, Guided by Tests - book by Freeman/Pryce Dunning-Kruger

Check out RailsClips on Kickstarter!!   01:56 - Testing and Test-Driven Development (TDD) The iPhreaks Show Episode #92: Unit Testing with NatashaTheRobot 03:23 - Panel Experiences with TDD Unit Testing The Difference Between Faking, Mocking, and Stubbing 08:10 - Value Objects 09:08 - How To Do TDD “Red, Green, Refactor” BDD (Behavior-Driven Development) The Cucumber Book: Behaviour-Driven Development for Testers and Developers  by Matt Wynne and Aslak Hellesøy The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends  by David Chelimsky, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, Dan North 11:28 - Jaim’s TDD Process 13:44 - Value and Getting Started with Testing Ruby Rogues Episode #178: Refactoring Ruby with Martin Fowler 21:58 - Writing Tests First “If Code is Easy to Test, It’s Easy to Change.” 27:18 - Testing on a Team Automation guard (Ruby) clang Continuous Integration (CI) 32:47 - Higher Level Testing 36:54 - KIF 38:00 - Other Ways of Testing UIs 39:44 - Who Writes the Tests? 44:06 - Test Data and Environments Test Time => Feedback 46:50 - Lower-level to Higher-level Tests Transition Value ROI (Return on Investment) 51:51 - Recording User Interactions Picks John Reid: UIViewController TDD [Screencast] (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) WatchKit FAQ (Alondo) This Idea Must Die: Scientific Theories That Are Blocking Progress (Edge Question Series) by John Brockman (Alondo) Martin Fowler: The Test Pyramid (Pete) Working Effectively with Unit Tests by Jay Fields (Pete) Avery Brewing IPA (Pete) A Wizard of Earthsea by Ursula K. Le Guin (Chuck) 80/20 Sales and Marketing: The Definitive Guide to Working Less and Making More by Perry Marshall (Chuck) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck)

Check out RailsClips on Kickstarter!!   01:56 - Testing and Test-Driven Development (TDD) The iPhreaks Show Episode #92: Unit Testing with NatashaTheRobot 03:23 - Panel Experiences with TDD Unit Testing The Difference Between Faking, Mocking, and Stubbing 08:10 - Value Objects 09:08 - How To Do TDD “Red, Green, Refactor” BDD (Behavior-Driven Development) The Cucumber Book: Behaviour-Driven Development for Testers and Developers  by Matt Wynne and Aslak Hellesøy The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends  by David Chelimsky, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, Dan North 11:28 - Jaim’s TDD Process 13:44 - Value and Getting Started with Testing Ruby Rogues Episode #178: Refactoring Ruby with Martin Fowler 21:58 - Writing Tests First “If Code is Easy to Test, It’s Easy to Change.” 27:18 - Testing on a Team Automation guard (Ruby) clang Continuous Integration (CI) 32:47 - Higher Level Testing 36:54 - KIF 38:00 - Other Ways of Testing UIs 39:44 - Who Writes the Tests? 44:06 - Test Data and Environments Test Time => Feedback 46:50 - Lower-level to Higher-level Tests Transition Value ROI (Return on Investment) 51:51 - Recording User Interactions Picks John Reid: UIViewController TDD [Screencast] (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) WatchKit FAQ (Alondo) This Idea Must Die: Scientific Theories That Are Blocking Progress (Edge Question Series) by John Brockman (Alondo) Martin Fowler: The Test Pyramid (Pete) Working Effectively with Unit Tests by Jay Fields (Pete) Avery Brewing IPA (Pete) A Wizard of Earthsea by Ursula K. Le Guin (Chuck) 80/20 Sales and Marketing: The Definitive Guide to Working Less and Making More by Perry Marshall (Chuck) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck)

While at NDC London, Carl and Richard talk to Ian Cooper about hexagonal architectures. Turns out the important part is not the six sides - it's the idea of ports and adapters. Originally talked about by Alistair Cockburn, this is an architectural approach that focuses on being tolerant to testing as well as separating commands from querying. It's not quite Command Query Responsibility Segregation (CQRS), but you can see it from there! Ian discusses testing in a hexagonal architecture and how Test Driven Development (TDD) works so well with the separation of concerns that ports and adapters offers. If you're working on a long lived application that needs to be maintainable, you should be looking at hexagonal architecture!Support this podcast at — https://redcircle.com/net-rocks/donations

While at NDC London, Carl and Richard talk to Ian Cooper about hexagonal architectures. Turns out the important part is not the six sides - it's the idea of ports and adapters. Originally talked about by Alistair Cockburn, this is an architectural approach that focuses on being tolerant to testing as well as separating commands from querying. It's not quite Command Query Responsibility Segregation (CQRS), but you can see it from there! Ian discusses testing in a hexagonal architecture and how Test Driven Development (TDD) works so well with the separation of concerns that ports and adapters offers. If you're working on a long lived application that needs to be maintainable, you should be looking at hexagonal architecture!Support this podcast at — https://redcircle.com/net-rocks/donations

Agile is a buzzword that, for better or worse, has caused emotional reactions that are both negative and positive. It is a highly overused and misunderstood term in our industry but it has shaped the way web software has been built for years. Agile is a flexible set of tools and practices that enable businesses to rapidly produce software that is extremely versatile to change. It has spawned many variants in its implementation and has endured much scrutiny. Agile strives to create quality software that embraces collaboration & individuals over interactions. James Shore (@JamesShore), creator of LetsCodeJavaScript.com (http://www.letscodejavascript.com/) and co-author of the book ‘The Art of Agile Development' (http://shop.oreilly.com/product/9780596527679.do), talks with us in our 6th episode - ‘What Agile Brings to Products & Teams -Why TDD is Not Dead'. This episode, at its core, is about Agile software development and how Test Driven Development (TDD) can help us, as programmers, build better quality software products & services. Development is not just about coding, it's about people and working together to build software that can easily change and adapt over time. The way we build products & services varies in techniques & implementation depending on the project. By using one or many Agile methodologies such as TDD we may be able to get there faster and with a better degree of maintainability, quality, and user experience. James is an author, thought leader, and software testing guru. He believes that great software development teams consistently deliver market success, technical success, and personal success for team members and stakeholders. He is one of the early pioneers of Agile software development and an incredible mentor.

SPaMCAST 295 features our essay on Test Driven Development (TDD). TDD is an approach to development in which you write a test that proves the piece of work you are working on, and then write the code required to pass the test. You then refactor that code to eliminate duplication and any overlap, then repeat until all of the work is completed. Philosophically, Agile practitioners see TDD as a tool either to improve requirements and design (specification) or to improve the quality of the code.  This is similar to the distinction between verification (are you doing the right thing) and validation (are you doing the thing right). We also have a new entry from the Software Sensei, Kim Pries. Kim addresses cognitive load theory.  Cognitive load theory helps explain how learning and change occur at personnel, team and organizational levels. Next week we will feature our interview with Jeff Dalton. Jeff and I talked about making Agile resilient.  Jeff posits that the CMMI can be used to strengthen and reinforce Agile. This is an important interview for organizations that are considering scaled Agile frameworks. Upcoming Events Upcoming DCG Webinars: July 24 11:30 EDT - The Impact of Cognitive Bias On Teams Check these out at www.davidconsultinggroup.com I will be attending Agile 2014 in Orlando, July 28 through August 1, 2014.  It would be great to get together with SPaMCAST listeners, let me know if you are attending. http://agile2014.agilealliance.org/ I will be presenting at the International Conference on Software Quality and Test Management in San Diego, CA on October 1 http://www.pnsqc.org/international-conference-software-quality-test-management-2014/ I will be presenting at the North East Quality Council 60th Conference October 21st and 22nd in Springfield, MA.  http://www.neqc.org/conference/60/location.asp More on all of these great events in the near future! I look forward to seeing all SPaMCAST readers and listeners that attend these great events!  The Software Process and Measurement Cast has a sponsor. As many you know I do at least one webinar for the IT Metrics and Productivity Institute (ITMPI) every year. The ITMPI provides a great service to the IT profession. ITMPI's mission is to pull together the expertise and educational efforts of the world's leading IT thought leaders and to create a single online destination where IT practitioners and executives can meet all of their educational and professional development needs. The ITMPI offers a premium membership that gives members unlimited free access to 400 PDU accredited webinar recordings, and waives the PDU processing fees on all live and recorded webinars. The Software Process and Measurement Cast some support if you sign up here. All the revenue our sponsorship generates goes for bandwidth, hosting and new cool equipment to create more and better content for you. Support the SPaMCAST and learn from the ITMPI. Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." Support SPaMCAST by buying the book here. Available in English and Chinese. 

SPaMCAST 294 features our interview with Sean Robson. We discussed his book, Agile%20SAP: Introducing flexibility, transparency and speed to SAP implementations" target="_blank">Agile SAP: Introducing flexibility, transparency and speed to SAP implementations. SAP and Agile, some say it can’t be done and they would just be wrong. Sean’s bio reads:Sean Robson, MBA, PMP, CSM, has been working with SAP software since 1998.  He started as an ABAP Developer then moved into configuring the Enterprise Asset Management module.  From there he transitioned to Business Warehouse and Portal support and later consulting where he worked as team lead, test manager and project manager. A Project Management Professional and Certified ScrumMaster, with wide consulting and industry experience, Sean has managed a variety of SAP project types and sizes. He has worked on projects in several industries throughout North America, including manufacturing, utilities, insurance, health care, aerospace and defense, and the public sector.  He currently works as an SAP Program Manager in the Insurance Industry. Sean’s contact Information:Email: sean.p.robson@gmail.comBlog: http://agilesap.wordpress.comBuy Sean’s book Agile%20SAP: Introducing flexibility, transparency and speed to SAP implementations" target="_blank">Agile SAP Thanks for the feedback on shortening the introduction of the cast this week. Please keep your feedback coming. Get in touch with us anytime or leave a comment here on the blog. Help support the SPaMCAST by reviewing and rating it on iTunes. It helps people find the cast. Like us on Facebook while you’re at it. Next week we will feature our essay covering Test Driven Development (TDD). TDD is a development technique that can help teams build the right thing right. Think about it and stop back next week!Upcoming EventsUpcoming DCG Webinars:June 19 11:30 EDT – How To Split User StoriesJuly 24 11:30 EDT - The Impact of Cognitive Bias On TeamsCheck these out at www.davidconsultinggroup.com I will be adding a long list of conferences I will be attending and/or speaking at in the near future. The first is Agile 2014, July 28 through August 1 in Orlando. Are you going? I look forward to seeing or hearing all SPaMCAST readers and listeners at this great event! The Software Process and Measurement Cast has a sponsor.As many you know I do at least one webinar for the IT Metrics and Productivity Institute (ITMPI) every year. The ITMPI provides a great service to the IT profession. ITMPI's mission is to pull together the expertise and educational efforts of the world's leading IT thought leaders and to create a single online destination where IT practitioners and executives can meet all of their educational and professional development needs. The ITMPI offers a premium membership that gives members unlimited free access to 400 PDU accredited webinar recordings, and waives the PDU processing fees on all live and recorded webinars. The Software Process and Measurement Cast some support if you sign up here. All the revenue our sponsorship generates goes for bandwidth, hosting and new cool equipment to create more and better content for you. Support the SPaMCAST and learn from the ITMPI. Shameless Ad for my book!Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." Support SPaMCAST by buying the book here.Available in English and Chinese.

A series of conversations between Kent Beck, David Heinemeier Hansson, and Martin Fowler on the topic of Test-Driven Development (TDD) and its impact upon software design. Episode 2: David feels that using TDD leads to approaches such as hexagonal rails that is test-induced design damage due to the complexity of excessive indirection. Kent thinks it's less about TDD and more about the quality of design decisions.

A series of conversations between Kent Beck, David Heinemeier Hansson, and Martin Fowler on the topic of Test-Driven Development (TDD) and its impact upon software design. In Episode #1, they talk about our varying experiences with the flow of TDD, and the way TDD and self-testing code are often confused.

James Grenning (@jwgrenning) joined Elecia to talk about how to be a good programmer using Test Driven Development (TDD). James' excellent book on how to use TDD: Test Driven Development for Embedded Systems  Take a class from Renaissance Software Manual test is not sustainable blog post, from James' blog Legacy code challenge from Github SOLID design principles Iterative and Incremental Development article by Craig Larman Untapped: the beer drinker's twitter To get the signed copy of James' book, email (show@embedded.fm), tweet (@logicalelegance), or hit the contact link on embedded.fm with your number between 0-99. First one with the correct number wins the book (if no one is correct, the closest number will be selected 12/25/13).