Podcasts about Unit testing

In dieser Episode des INNOQ Podcasts diskutieren Daniel Westheide, Jakob Oswald und Sven Johann über das Für und Wider verschiedener Teststrategien. Ausgehend von einer internen Debatte bei INNOQ gehen die drei der Frage nach, wie viel Gewicht auf Unit Tests, Integrationstests oder exploratives Testen gelegt werden sollte – und was die Domäne damit zu tun hat. Sie sprechen über transaktionale Fallstricke, überflüssige Redundanz durch überambitionierte Testabdeckung und persönliche Erfahrungen aus regulierten Projekten. Am Ende steht kein Dogma, sondern ein differenziertes Bild: zwischen Testpyramide, Testdiamant und gesundem Pragmatismus.

Fuzzing: Software-Stabilität durch Zufalls-generierte EingabedatenTesten, besonders automatisiertes Testen der eigenen Software, gilt als Best Practice in der Softwareentwicklung. Egal, ob wir dabei von Unit-Testing, Integration Testing, Funktions- oder Akzeptanztesting sprechen. Die Idee dabei ist, dass wir die Fehler in der Software gering halten. Auch wenn deine Tests zu einer 100%igen Code Coverage führen, heißt es nicht, dass dein Programm keine Bugs hat. Denn ein Problem gibt es bei all diesen Test-Arten: Die Input-Parameter sind i.d.R. nach einer gewissen Struktur erstellt worden. Und dies heißt noch lange nicht, dass diese Input-Parameter alle möglichen Fälle abdecken.Und genau da kommt das Thema Fuzzing bzw. Fuzz-Testing ins Spiel. Das Testen deiner Software mit zufällig generierten Input-Parametern. Das klingt erstmal wild, kann aber ganz neue Probleme in deiner Software aufdecken. Und das ist das Thema in dieser Episode.Zu Gast ist Prof. Dr. Andreas Zeller, Forscher im Bereich Softwaretesting und Autor des Fuzzing Books. Mit ihm klären wir, was Fuzzing eigentlich ist, woher es kommt und wie es sich gegenüber anderen Teststrategien, wie Unit-Testing, verhält. Er gibt uns einen Einblick in die Unterschiede von Search-Based Fuzzing, Grammar-Fuzzing, Symbolic Fuzzing sowie spezifikationsbasierten Fuzzern, wie komplexe Systeme mittels metamorphes Testen verbessert werden können, was das Orakel-Problem ist, wie z.B. Datenbanken gefuzzed werden können, aber auch wie das Ganze in der Praxis angewendet werden kann und wie du einfach mit Fuzzing starten kannst.Bonus: Was ein Orakel mit Testing zu tun hat.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

W pierwszym odcinku w 2025 roku zapraszam na pierwszą odsłonę Backend vs Frontend, gdzie wspólnie z Tomkiem Ducinem bedziemy pochylać się nad różnymi problemami związanymi z software developmentem. Na początek temat testowania i testów integracyjnych, bo jeśli nie testujesz swojego kodu, to jak możesz mieć pewność, że wszystko działa poprawnie?Ale “hold your horses”… testy to tylko przyczynek do tego, aby porozmawiać w luźnej atmosferze o wielu ważnych rzeczach dookoła.

Have you ever wondered why Extreme Programming (XP) isn't commonly taught in schools? In this engaging episode of the Mob Mentality Show, we dive into this intriguing question brought to us by the mob programming community.

How do you test your database? While at NDC Porto, Richard chatted with Dan Mallott about building unit tests for transactional databases like SQL Server. Dan talks about using testing frameworks constructed for the purpose, like TSQL-T, to make it easier to test individual database elements, from stored procedures to column constraints. The conversation digs into the challenges around testing, tolerating the changes to the database, and tweaking how you write your T-SQL code to be more testable. But the power of getting database tests into your CI/CD pipeline is enormous - catch more problems in testing before they become problems in production!LinkstsqltDbFitRecorded October 17, 2024

In this episode of the Modern Web Podcast, host Rob Ocel and co-hosts Adam Rackis, Tracy Lee, and Danny Thompson discuss the importance of unit testing for maintaining code quality and reliability, emphasizing its role in scaling projects and ensuring long-term stability. The conversation also highlights the benefits of TypeScript in improving code safety and developer productivity, sharing experiences on how it catches errors early in the process. They also examine the growing role of AI in automating development tasks, weighing the efficiency gains against the risks of over-reliance on automation while stressing the importance of understanding the underlying processes. Chapters 00:00 - Introduction and Episode Overview 02:59 - The Importance of Unit Testing 10:03 - Best Practices for Implementing Unit Tests 17:15 - TypeScript's Role in Code Safety and Productivity 2:30 - AI in Software Development: Automating Tasks 29:16 - Balancing AI Automation with Developer Expertise 32:07 - Final Thoughts and Closing Remarks Sponsored by This Dot: thisdot.co

React and JavaScript expert Cory House discusses the creation of custom development tools for React applications, sharing insights from his recent talk at React Rally and exploring how the right tools can shape development workflows and enhance automated testing strategies. Links https://www.bitnative.com https://github.com/coryhouse/ama https://x.com/housecor https://github.com/coryhouse https://stackoverflow.com/users/26180/cory-house https://www.linkedin.com/in/coryhouse https://www.pluralsight.com/authors/cory-house https://www.reactjsconsulting.com We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Cory House.

Ecco un argomento molto discusso, molti li conoscono ma pochi li usano. Con la puntata di oggi voglio dare il via ad un percorso alla scoperta del mondo dei Test, iniziando oggi con un'introduzione agli Unit Test.https://amzn.to/3TdJFJIhttps://learn.microsoft.com/en-us/visualstudio/test/unit-test-basics?view=vs-2022https://learn.microsoft.com/en-us/visualstudio/test/create-unit-tests-menu?view=vs-2022#visualstudio #unittest #dotnetinpillole #podcast #xunit #nunit #mstest

On this episode of The Main Scoop, we are joined by Bertrand Cardinal, Director of Banking Solutions at Desjardins, for a conversation on empowering development teams through automation, unit testing, and collaboration. We discuss how applications are the keys to harnessing the power of the mainframe, making developers gatekeepers who must be empowered to deliver more, maximize productivity, and ensure applications deliver ongoing vitality. This developer-centric approach is crucial for leveraging the full potential of technology in banking.  

Testing ist nicht gleich Testing - Ein Deep Dive mit Sebastian BergmannViele Software-Entwickler⋅innen kennen Unit-Tests. Einige schreiben Unit Tests bei der Entwicklung. Wenige machen wirklich Test-Driven-Development. Doch beim Unit-Testing fängt das ganze Thema Testing doch erst an. Wie sieht es denn mit Static Testing, Non-Functional-Testing, White-Box-Testing, End-to-End-Testing, Dynamic Testing oder Integration Testing aus? Und hast du schon mal von Mutanten Testing gehört?Ganz schön viele Buzzwords. Und dabei haben wir noch gar nicht die Fragen beantwortet, was eigentlich gute Tests sind, wie viele Tests genug Tests sind, wie AI uns helfen kann bessere Tests zu schreiben oder ob Testing eigentlich moderner Kram ist oder schon seit Anbeginn des Programmier Zeitalters eine Rolle gespielt hat.In dieser Episode gibt es einen Rundumschlag zum Thema Testing mit Sebastian Bergmann.Bonus: Die Amiga-Szene lebt.Das schnelle Feedback zur Episode:

In this conversation, Myles Gray discusses the AI workflow and its personas, the responsibilities of data scientists and developers in deploying AI models, the role of infrastructure administrators, and the challenges of deploying models at the edge. He also explains the concept of quantization and the importance of accuracy in models. Additionally, he talks about the pipeline for deploying models and the difference between unit testing and integration testing. Unit testing is used to test the functionality of a single module or function within an application. Integration testing involves testing the interaction between different components or applications. MLflow and other tools are used to store and manage ML models. Smaller models are emerging as a solution to the resource constraints of large models. Collaboration between different personas is important for ensuring security and governance in AI projects. Data governance policies are crucial for maintaining data quality and consistency.TakeawaysThe AI workflow involves multiple personas, including data scientists, developers, and infrastructure administrators.Data scientists play a crucial role in developing AI models, while developers are responsible for deploying the models into production.Infrastructure administrators need to consider the virtualization layer and ensure efficient and easy consumption of infrastructure components.Deploying AI models at the edge requires quantization to reduce model size and considerations for form factor, scale, and connectivity.The pipeline for deploying models involves steps such as unit testing, scanning for vulnerabilities, building container images, and pushing to a registry.Unit testing focuses on testing individual components, while integration testing ensures the compatibility and functionality of the entire system. Unit testing is used to test the functionality of a single module or function within an application.Integration testing involves testing the interaction between different components or applications.MLflow and other tools are used to store and manage ML models.Smaller models are emerging as a solution to the resource constraints of large models.Collaboration between different personas is important for ensuring security and governance in AI projects.Data governance policies are crucial for maintaining data quality and consistency.Chapters00:00 Understanding the AI Workflow and Personas03:24 The Role of Data Scientists and Developers in Deploying AI Models08:47 The Responsibilities of Infrastructure Administrators15:25 Challenges of Deploying Models at the Edge20:29 The Pipeline for Deploying AI Models24:45 Unit Testing vs. Integration Testing28:22 Managing ML Models with MLflow and Other Tools32:17 The Emergence of Smaller Models39:58 Collaboration for Security and Governance in AI Projects46:32 The Importance of Data GovernanceDisclaimer: The thoughts and opinions shared in this podcast are our own/guest(s), and not necessarily those of Broadcom or VMware by Broadcom.

Today on Elixir Wizards Office Hours, SmartLogic Engineer Joel Meador joins Dan Ivovich to discuss all things background jobs. The behind-the-scenes heroes of app performance and scalability, background jobs take center stage as we dissect their role in optimizing user experience and managing heavy-lifting tasks away from the main application flow. From syncing with external systems to processing large datasets, background jobs are pivotal to successful application management. Dan and Joel share their perspectives on monitoring, debugging, and securing background jobs, emphasizing the need for a strategic approach to these hidden workflows. Key topics discussed in this episode: The vital role of background jobs in app performance Optimizing user experience through background processing Common pitfalls: resource starvation and latency issues Strategies for effective monitoring and debugging of task runners and job schedulers Data integrity and system security in open source software Background job tools like Oban, Sidekiq, Resque, Cron jobs, Redis pub sub CPU utilization and processing speed Best practices for implementing background jobs Keeping jobs small, focused, and well-monitored Navigating job uniqueness, locking, and deployment orchestration Leveraging asynctask for asynchronous operations The art of continuous improvement in background job management Links mentioned in this episode: https://redis.io/ Oban job processing library https://hexdocs.pm/oban/Oban.html Resque Ruby library for background jobs https://github.com/resque Sidekiq background processing for Ruby https://github.com/sidekiq Delayed Job priority queue system https://github.com/collectiveidea/delayed_job RabbitMQ messaging and streaming broker https://www.rabbitmq.com/ Mnesia distributed telecommunications DBMS https://www.erlang.org/doc/man/mnesia.html Task for Elixir https://hexdocs.pm/elixir/1.12/Task.html ETS in-memory store for Elixir and Erlang objects https://hexdocs.pm/ets/ETS.html Cron - https://en.wikipedia.org/wiki/Cron Donate to Miami Indians of Indiana https://www.miamiindians.org/take-action Joel Meador on Tumblr https://joelmeador.tumblr.com/ Special Guest: Joel Meador.

Jeśli wycena projektu podawana jest w dwóch wersjach, z uwzględnieniem testów i bez, to z software craftsmanshipem ma to niewiele wspólnego. To tak, jakby pytać chirurga, czy może przyspieszyć operację nie dezynfekując skalpela. Jakość nie powinna być elementem przetargowym. Chyba, że pracujemy nad proof-of-concept, ale tego rodzaju projekty często lubią płynnie przejść w fazę protoduction...Jeśli szukasz sprawdzonych w boju receptur na implementację jakościowych testów, które nie będą wymagały co chwilę refaktoryzacji i modyfikacji przy zmianie kodu projektu, zapraszam Cię na dzisiejszą rozmowę z Piotrem Stawirejem. Napisać test w projekcie to w zasadzie żadna sztuka. Ale napisać test, który dostarczy realną wartość biznesową, będzie łatwy do utrzymania, a przy okazji może zostać wykorzystany na różnych poziomach piramidy testów, to trochę bardziej skomplikowane zadanie.I pewnie niektóre strategie mogą być trochę kontrowersyjne, jak na przykład rezygnacja z typowego mockowania zależności, czy silnego podziału na wiele różnych testów w projekcie. Ale skoro działa to w praktyce, to w czym rzecz?W tym odcinku rozmawiamy wraz z Piotrem między innymi o:organizacyjnych i technicznych problemach z implementacją jakościowych testów w backendziemetryce code-coverage i jej różnym stopniu przydatności w projekcieprofesjonalnym podejściu do problemu "z testami, czy bez?"dobrych praktykach doboru strategii testowaniaszarej strefie testów Kevlina Henney'alegacy, testach charakterystyki, szwach i odcinaniu fragmentów systemu dla testówunitach, czyli fragmentach kodu o pojedynczej odpowiedzialności, mierzonego kohezjąimplementacji architektury otwartej na testowanieeliminacji problemów z nadużywaniem mocków w projekcieZapraszam!Materiały dodatkowe:Sub-second acceptance tests, prezentacja Aslaka Hellesøy z konferencji SeleniumConf ChicagoGrowing Object-Oriented Software, Guided by Tests, wspomniana w rozmowie książka Steve'a Freemana i Nata Pryce'aStyle Guide for Object Design, książka Matthiasa NobackaFinancial System, repozytorium z przykładowym kodem Piotra

In Elixir Wizards Office Hours Episode 2, "Discovery Discoveries," SmartLogic's Project Manager Alicia Brindisi and VP of Delivery Bri LaVorgna join Elixir Wizards Sundi Myint and Owen Bickford on an exploratory journey through the discovery phase of the software development lifecycle. This episode highlights how collaboration and communication transform the client-project team dynamic into a customized expedition. The goal of discovery is to reveal clear business goals, understand the end user, pinpoint key project objectives, and meticulously document the path forward in a Product Requirements Document (PRD). The discussion emphasizes the importance of fostering transparency, trust, and open communication. Through a mutual exchange of ideas, we are able to create the most tailored, efficient solutions that meet the client's current goals and their vision for the future. Key topics discussed in this episode: Mastering the art of tailored, collaborative discovery Navigating business landscapes and user experiences with empathy Sculpting project objectives and architectural blueprints Continuously capturing discoveries and refining documentation Striking the perfect balance between flexibility and structured processes Steering clear of scope creep while managing expectations Tapping into collective wisdom for ongoing discovery Building and sustaining a foundation of trust and transparency Links mentioned in this episode: https://smartlogic.io/ Follow SmartLogic on social media: https://twitter.com/smartlogic Contact Bri: bri@smartlogic.io What is a PRD? https://en.wikipedia.org/wiki/Productrequirementsdocument Special Guests: Alicia Brindisi and Bri LaVorgna.

The Elixir Wizards Podcast is back with Season 12 Office Hours, where we talk with the internal SmartLogic team about the stages of the software development lifecycle. For the season premiere, "Testing 1, 2, 3," Joel Meador and Charles Suggs join us to discuss the nuances of software testing. In this episode, we discuss everything from testing philosophies to test driven development (TDD), integration, and end-user testing. Our guests share real-world experiences that highlight the benefits of thorough testing, challenges like test maintenance, and problem-solving for complex production environments. Key topics discussed in this episode: How to find a balance that's cost-effective and practical while testing Balancing test coverage and development speed The importance of clear test plans and goals So many tests: Unit testing, integration testing, acceptance testing, penetration testing, automated vs. manual testing Agile vs. Waterfall methodologies Writing readable and maintainable tests Testing edge cases and unexpected scenarios Testing as a form of documentation and communication Advice for developers looking to improve testing practices Continuous integration and deployment Links mentioned: https://smartlogic.io/ Watch this episode on YouTube! youtu.be/unx5AIvSdc Bob Martin “Clean Code” videos - “Uncle Bob”: http://cleancoder.com/ JUnit 5 Testing for Java and the JVM https://junit.org/junit5/ ExUnit Testing for Elixir https://hexdocs.pm/exunit/ExUnit.html Code-Level Testing of Smalltalk Applications https://www.cs.ubc.ca/~murphy/stworkshop/28-7.html Agile Manifesto https://agilemanifesto.org/ Old Man Yells at Cloud https://i.kym-cdn.com/entries/icons/original/000/019/304/old.jpg TDD: Test Driven Development https://www.agilealliance.org/glossary/tdd/ Perl Programming Language https://www.perl.org/ Protractor Test Framework for Angular and AngularJS protractortest.org/#/ Waterfall Project Management https://business.adobe.com/blog/basics/waterfall CodeSync Leveling up at Bleacher Report A cautionary tale - PETER HASTIE https://www.youtube.com/watch?v=P4SzZCwB8B4 Mix ecto.dump https://hexdocs.pm/ectosql/Mix.Tasks.Ecto.Dump.html Apache JMeter Load Testing in Java https://jmeter.apache.org/ Pentest Tools Collection - Penetration Testing https://github.com/arch3rPro/PentestTools The Road to 2 Million Websocket Connections in Phoenix https://www.phoenixframework.org/blog/the-road-to-2-million-websocket-connections Donate to Miami Indians of Indiana https://www.miamiindians.org/take-action Joel Meador on Tumblr https://joelmeador.tumblr.com/ Special Guests: Charles Suggs and Joel Meador.

.

.

In this podcast episode, we discuss how testing is becoming more human-like across all levels, including API and Unit tests, driven by new tools that focus on real-world scenarios. We debunk the myth that design skills are innate, showing how they're rooted in science and can be learned like any other skill. Topics like color theory and psychological principles are highlighted for their role in enhancing developer skills. Finally, we examine the rapid growth of the low-code market, projecting that 65% of applications will use no-code solutions by 2024, leading to a significant shift in application development and management.Stay updated with new weekly episodes every Thursday – and don't forget to subscribe! For more behind-the-scenes content, follow us @justshiftleft on Facebook, Instagram, Twitter, and LinkedIn.

On today's episode, Elixir Wizards Owen Bickford and Dan Ivovich compare notes on building web applications with Elixir and the Phoenix Framework versus Ruby on Rails. They discuss the history of both frameworks, key differences in architecture and approach, and deciding which programming language to use when starting a project. Both Phoenix and Rails are robust frameworks that enable developers to build high-quality web apps—Phoenix leverages functional programming in Elixir and Erlang's networking for real-time communication. Rails follows object-oriented principles and has a vast ecosystem of plug-ins. For data-heavy CRUD apps, Phoenix's immutable data pipelines provide some advantages. Developers can build great web apps with either Phoenix or Rails. Phoenix may have a slight edge for new projects based on its functional approach, built-in real-time features like LiveView, and ability to scale efficiently. But, choosing the right tech stack depends heavily on the app's specific requirements and the team's existing skills. Topics discussed in this episode: History and evolution of Phoenix Framework and Ruby on Rails Default project structure and code organization preferences in each framework Comparing object-oriented vs functional programming paradigms CRUD app development and interaction with databases Live reloading capabilities in Phoenix LiveView vs Rails Turbolinks Leveraging WebSockets for real-time UI updates Testing frameworks like RSpec, Cucumber, Wallaby, and Capybara Dependency management and size of standard libraries Scalability and distribution across nodes Readability and approachability of object-oriented code Immutability and data pipelines in functional programming Types, specs, and static analysis with Dialyzer Monkey patching in Ruby vs extensible core language in Elixir Factors to consider when choosing between frameworks Experience training new developers on Phoenix and Rails Community influences on coding styles Real-world project examples and refactoring approaches Deployment and dev ops differences Popularity and adoption curves of both frameworks Ongoing research into improving Phoenix and Rails Links Mentioned in this Episode: SmartLogic.io (https://smartlogic.io/) Dan's LinkedIn (https://www.linkedin.com/in/divovich/) Owen's LinkedIn (https://www.linkedin.com/in/owen-bickford-8b6b1523a/) Ruby https://www.ruby-lang.org/en/ Rails https://rubyonrails.org/ Sams Teach Yourself Ruby in 21 Days (https://www.overdrive.com/media/56304/sams-teach-yourself-ruby-in-21-days) Learn Ruby in 7 Days (https://www.thriftbooks.com/w/learn-ruby-in-7-days---color-print---ruby-tutorial-for-guaranteed-quick-learning-ruby-guide-with-many-practical-examples-this-ruby-programming-book--to-build-real-life-software-projects/18539364/#edition=19727339&idiq=25678249) Build Your Own Ruby on Rails Web Applications (https://www.thriftbooks.com/w/build-your-own-ruby-on-rails-web-applications_patrick-lenz/725256/item/2315989/?utm_source=google&utm_medium=cpc&utm_campaign=low_vol_backlist_standard_shopping_customer_acquisition&utm_adgroup=&utm_term=&utm_content=593118743925&gad_source=1&gclid=CjwKCAiA1MCrBhAoEiwAC2d64aQyFawuU3znN0VFgGyjR0I-0vrXlseIvht0QPOqx4DjKjdpgjCMZhoC6PcQAvD_BwE#idiq=2315989&edition=3380836) Django https://github.com/django Sidekiq https://github.com/sidekiq Kafka https://kafka.apache.org/ Phoenix Framework https://www.phoenixframework.org/ Phoenix LiveView https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html#content Flask https://flask.palletsprojects.com/en/3.0.x/ WebSockets API https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API WebSocket connection for Phoenix https://github.com/phoenixframework/websock Morph Dom https://github.com/patrick-steele-idem/morphdom Turbolinks https://github.com/turbolinks Ecto https://github.com/elixir-ecto Capybara Testing Framework https://teamcapybara.github.io/capybara/ Wallaby Testing Framework https://wallabyjs.com/ Cucumber Testing Framework https://cucumber.io/ RSpec https://rspec.info/

EPISODE DESCRIPTION:Watch out for Cupid, we're all falling in LOVE over here at the Dev Life!... ng-conf speaker and mentoring guru at World Class Engineers, Joe Skeen, Joins this episode for a heart-filled dive into the commonly unloved practice of Unit Testing. We talk about proven strategies for unit testing, common pitfalls, favorite tools and libraries, unit testing with AI, and SOoo much more! From the first Expect to the final Assertion, get ready to fall head over heels with unit tests of your own! This is... the Dev Life!LINKS:https://twitter.com/joeskeenjrhttps://www.worldclassengineers.dev/Joe Skeen – MediumCONNECT WITH US:Joe Skeen - @joeskeenjrBrooke Avery - @jediBraveryPreston Lamb - @joeskeenjr

In this episode, Matt and Eric discuss their current projects and what technologies they are learning. They take a dive into behavioral lessons, working with Stripe and Unit Testing, and the recently released NextJS 13 App Router. Matt's Links: https://mehrlich-link-tree.netlify.app/ Eric's Links: https://linktr.ee/ericwinkdev

Should you delegate unit testing to junior devs?

“As a team leader, you will become more successful and valuable if you are no longer a bottleneck for the people who are working with you and under you." Roy Osherove is the author of “Elastic Leadership” and “The Art of Unit Testing”. In this episode, we discussed leadership insights from “Elastic Leadership”. Roy first shared how he came up with the concept and described what elastic leadership is. He explained the different leadership styles based on the 3 team phases (survival mode, learning mode, and self-organizing mode) and advised how leaders can adapt and transition their leadership style from one phase to the other to lead effectively. Roy also shared about the Team Leader manifesto and the Line Manager manifesto to provide guidance on how leaders can grow their teams towards self-organization and self-sufficiency. Listen out for: Career Journey - [00:06:45] Writing “Elastic Leadership” - [00:11:31] Team Leader Manifesto - [00:17:57] There Are No Experts - [00:23:23] Survival Mode - [00:30:49] Slack Time - [00:37:52] Self-Organizing Mode - [00:39:21] Learning Mode - [00:41:18] Line Manager Manifesto - [00:45:47] 3 Tech Lead Wisdom - [00:48:13] _____ Roy Osherove's Bio Roy Osherove is the organizer of the CD/XP Israel meetup group. He's the author of “Art of Unit Testing”, “Elastic Leadership” and the upcoming “Co-Ops: Pipeline Driven Organizations”. He has been working in the software industry for over 20 years in most types of technical & testing roles, and these days is working as a freelance consultant & trainer on-site for various companies across the world. Follow Roy: Twitter – @RoyOsherove LinkedIn – https://linkedin.com/in/osherove/ Website – https://osherove.com/ 5 Whys – https://5whys.com/ Our Sponsors Mental well-being is a silent pandemic. According to the WHO, depression and anxiety cost the global economy over USD 1 trillion every year. It's time to make a difference! Learn how to enhance your lives through a master class on mental wellness. Visit founderswellbeing.com/masterclass and enter TLJ20 for a 20% discount. The iSAQB® Software Architecture Gathering is the international conference highlight for all those working on solution structures in IT projects: primarily software architects, developers, professionals in quality assurance, and also system analysts. The conference takes place online from November 14 to 17, 2022, and we have a 15% discount code for you: TLJ_MP_15. DevTernity 2022 (devternity.com) is the top international software development conference with an emphasis on coding, architecture, and tech leadership skills. The lineup is truly stellar and features many legends of software development like Robert "Uncle Bob" Martin, Kent Beck, and many others! The conference takes place online, and we have the 10% discount code for you: AWSM_TLJ. Like this episode? Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For episode show notes, visit techleadjournal.dev/episodes/110.

Consigue cursos y contenido extra en mi pagina de https://conexiones.captivate.fm/gumroad (Gumroad): https://conexiones.captivate.fm/gumroad Unete a nuestra comunidad de Conectores: En Discord: https://conexiones.captivate.fm/discord En Slack: https://conexiones.captivate.fm/slack En Este Episodio: Conversamos con Camila Lenis (@ladivaloper) sobre su experiencia haciendo un curso para Platzi, la escuela en linea más grande de America Latina. Nos conto cómo fue el proceso desde escoger el tema hasta lanzarlo en la plataforma. También nos conto sobre su nuevo startup Noh, donde es Founding Developer, y cómo quieren simplificar la manera en que la gente comparte gastos en Brasil. Puedes conectar con Camila via https://www.linkedin.com/in/camilaleniss ## Notas del Show - Curso de Camila sobre Unit Testing en Vue.js 3 https://platzi.com/cursos/go-unit-testing/ - Curso de Camila sobre Unit Testing en Go: https://platzi.com/cursos/go-unit-testing/ - Aprende a usar Scratch - https://www.youtube.com/watch?v=u6s1AiYcLs8&ab_channel=Honestips%28Espa%C3%B1ol%29 - Conoce a Noh - Para dividir contas e juntar pessoas https://www.noh.com.br/ ¿Quieres ser parte de mi newsletter? (En Ingles) Puedes unirte por https://lwt-email.ck.page/a586968cfb (aquí)

How to unit-test a graphical component? For example, how to unit-test a map or a chart in React since there is no text to select and to run tests against? Testing a graphical component

in response to this tweet: https://twitter.com/Rovolutionary/status/1564338893691953154 Question about testing a reusable component

Agile software development requires fast feedback from testing. Unit tests are one of the most important tests among different testing levels and can return quick results compared with other tests. Although QA testers are not involved in unit testing, they should understand what it is to define effective and efficient testing strategies. This podcast will give the audience a QA perspective on Unit testing. Host: Chamal Perera, Senior QA Lead, 99x Speaker: Ruwanthi Soysa, Associate Architect (Test automation), 99x

Servono davvero i test? Perchè li dovremmo scrivere? Vediamo di parlare un pò di questo argomento così sconosciuto, ma di assoluta importanza, specialmente per chi vuole realizzare software che duri nel tempo.https://it.wikipedia.org/wiki/Unit_testinghttps://docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-dotnet-test?WT.mc_id=DT-MVP-4021952https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps?WT.mc_id=DT-MVP-4021952https://amerlin.keantex.com/unit-test-in-asp-core-parte-1/

You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer. 

Das Thema Testing begleitet uns seit vielen Jahren. Glücklicherweise scheint es immer leichter zu werden. Joe Ray Gregory (Twitter / Website), Senior Software Engineer und Trainier bei workshops.de, b…

Das Thema Testing begleitet uns seit vielen Jahren. Glücklicherweise scheint es immer leichter zu werden. Joe Ray Gregory (Twitter / Website), Senior Software Engineer und Trainier bei workshops.de, bringt uns diesmal das Framework Testing Library mit. Psst, Geheimtipp: Joe verrät uns, dass es aktuell Early Bird Tickets für die Vue.js Konferenz in Berlin am 22. […]

In the second episode of The Snippet Series Artur is giving his insights into the topic of proper sizing "unit" for Unit Testing.How to make Unit Testing well-grained? Is every piece of code worth having separate test suite? What to do when the size of your test files overwhelm you? You can find answers to those questions in the episode.00:00 Intro

In this week's installment of Programming By Stealth, Bart takes us down memory lane to 102 episodes ago when he first introduced us to the concept of test-driven development. He explains why back then he taught us how to use QUnit for our TDD work, and why it's no longer in favor with him. It's not just the advancements in technology like ES6, but it's also because QUnit makes it terribly hard to write tests and to interpret what you've written when you've been away from it for a while. He walks us through his criteria for picking a new TDD tool, and why he chose Jest for the job. He then walks us through a worked example of how to write some simple tests on a module and of course, explains how Jest does its job running our tests. I liked it, even though my head hurt during a bit of it! You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.

In this week's installment of Programming By Stealth, Bart takes us down memory lane to 102 episodes ago when he first introduced us to the concept of test-driven development. He explains why back then he taught us how to use QUnit for our TDD work, and why it's no longer in favor with him. It's not just the advancements in technology like ES6, but it's also because QUnit makes it terribly hard to write tests and to interpret what you've written when you've been away from it for a while. He walks us through his criteria for picking a new TDD tool, and why he chose Jest for the job. He then walks us through a worked example of how to write some simple tests on a module and of course, explains how Jest does its job running our tests. I liked it, even though my head hurt during a bit of it! You can find Bart's fabulous tutorial shownotes at pbs.bartificer.net.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRoy Osherove - Author of "The Art of Unit Testing"Dave Farley - Co-Author of "Continuous Delivery"You can find more content like this on Dave's "Continuous Delivery YouTube Channel": https://www.youtube.com/channel/UCCfqyGl3nq_V0bo64CjZh8gDESCRIPTIONGood tests are crucial to any software project, and having a test-driven approach should be part of most projects' goals nowadays. Yet testing can be difficult due to its complexity and challenges. Join a deep dive on how to approach unit testing with the author of “The Art of Unit Testing,” Roy Osherove, and a strong promoter of test-driven design, Dave Farley.The interview is based on Roy's book "The Art of Unit Testing": https://bit.ly/3obiKNBRead the full transcription of the interview here:https://gotopia.tech/bookclub/episodes/getting-started-with-unit-testingRECOMMENDED BOOKSRoy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNBRoy Osherove • Elastic Leadership • https://amzn.to/3fxEgIDRoy Osherove • Notes to a Software Team Leader • https://amzn.to/3wjroxJDave Farley & Jez Humble • Continuous Delivery • https://amzn.to/3ocIHwdDavid Farley • Modern Software Engineering • https://amzn.to/3GI468MDavid Farley • Continuous Delivery Pipelines • https://leanpub.com/cd-pipelinesPatterson, Grenny, Maxflied, McMillan & Switzler • Influencer: The Power to Change Anything • https://amzn.to/3hMGrdUhttps://twitter.com/GOTOconhttps://www.linkedin.com/company/goto-https://www.facebook.com/GOTOConferencesLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at https://gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

Jon and I share some memories before we dive into his history. Jon is one of those mellow friendly persons who will just wait for you to start asking questions. And once you do, be ready for the wealth of knowledge and detail you will get as a response.Jon also wrote a book on iOS unit testing. Nowadays Jon works at Industrial Logic and by how he describes it, Jon has found his tribe.Quality CodingiOS Unit Testing by Example: XCTest Tips and Techniques Using Swift by Jon ReidExtreme Programming RoadmapJon Reid on Industrial LogicApprovalTests for Swift, an alternative to assertions on GitHub QCoding - TwitchLive TDD in Swift (Survey Analyzer) - YouTubeThe workshop Jon and I were doing at the start of the pandemicPlease rate me on Apple Podcasts.Send me feedback on SpeakPipeOr contact me through twitterNewsletter, sign up!My book: Being a Lead Software DeveloperRunwayPut your mobile releases on autopilot and keep the whole team in sync throughout. Lead Software Developer Learn best practices for being a great lead software developer.Support the show (https://pod.fan/appforce1)

This interview was recorded at GOTO Copenhagen 2021 for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/the-future-of-devopsPJ Hagerty - Head of DevRel at MattermostHanna Park - Workplace Community Manager at MattermostDESCRIPTIONThe pandemic and remote work have changed the direction of the DevOps movement. Find out what lies ahead with Hanna Park, community manager at Mattermost, and PJ Hagerty, head of developer relations at Mattermost, in their discussion at GOTO Copenhagen 2021.RECOMMENDED BOOKSForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOps • https://amzn.to/3tCz1xOJohn Arundel & Justin Domingus • Cloud Native DevOps with Kubernetes • https://amzn.to/3hKZvI5Wynne, Hellesoy & Tooke • The Cucumber Book • https://amzn.to/3tEUINJRobert C. Myers • Essential Test-Driven Development • https://amzn.to/2Xc8ZWaRoy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNBEric Ries • The Lean Startup • https://amzn.to/396fOvaRonnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• https://amzn.to/3c4HmmLhttps://twitter.com/GOTOconhttps://www.linkedin.com/company/goto-https://www.facebook.com/GOTOConferencesLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at https://gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

Array Cast - November 13, 2021 Show NotesLink to presentation resources of Dialog ‘21 https://www.dyalog.com/user-meetings/dyalog21.htm00:00:30 Dyalog User Meeting '21: https://www.dyalog.com/user-meetings/dyalog21.htm00:03:03 Richard Park's presentation on the Dyalog Media Update: TBA00:04:10 ShapeRank: https://github.com/f5devcentral/shapeRank00:05:50 Gitte on Array Cast: https://www.arraycast.com/episodes/episode12-gitte-christensen00:07:45 Brian Becker's presentation about Packaging Dyalog Tools / Tatin: TBA00:09:05 Hashback #! scripting presentation: TBA00:09:05 Link presentation: TBA00:11:27 Rodrigo's presentation on Py'n'APL: TBA00:14:10 C++ compiler explorer: https://godbolt.org/00:21:00 Ken Iverson's “Notation as a Tool of Thought” Paper (pdf): https://www.eecg.utoronto.ca/~jzhu/csc326/readings/iverson.pdf00:27:21 Kimmo Linna's RSConnect: https://github.com/kimmolinna/rsconnect00:29:15 TamStat: http://www.tamstat.com/00:33:24 CodeGolf website: http://codegolf.stackexchange.com/00:33:59 The APL Orchard: The APL Orchard00:53:51 Aaron Hsu on “The Fallacy of Unit Testing”: https://www.sacrideo.us/the-fallacy-of-unit-testing/

In this episode of the podcast (for non-beginners), we look at why most people believe they're struggling with unit testing and what's actually happening instead. This is the Java Easily Podcast where beginning and intermediate Java developers can get all the latest tips, tutorials and advice on Java software development. Check out our courses at ⁠https://courses.javaeasily.com⁠ Get your Java Beginner's Starter Kit over at ⁠https://javaeasily.com⁠

Diffblue, a spin-out from Oxford University, uses machine learning to help developers automatically create unit tests for their Java code. Since few developers enjoy writing unit tests to ensure that their code works as expected, increased automation doesn't just help developers focus on writing the code that actually makes a difference but also lead to […]

In this four-part series, the Angular Show breaks down testing in Angular. Do you test? Should you have automated tests? And if you do test, what types of tests should you implement? Should you unit test? Should you have end-to-end tests? What about integration tests? This series tackles all of these questions and more.In part one, panelists Aaron Frost and Jennifer Wadella invite Joe Eames, CEO of Thinkster.io and Pluralsight author, along with Shai Reznik, founder and author of testangular.com, to share their knowledge and love of unit testing in Angular.While you are most likely performing manual testing, you may not be leveraging automated testing. Automated testing enables us to prevent regressions, increasing the quality of our applications. While many of us may not be leveraging automated testing, it can be extremely valuable when moving fast, when we have multiple developers on a team or in the code base, and perhaps even multiple teams in an organization that is sharing the same code and repository. The end result is confidence. Having a high level of confidence in shipping quality software provides significant value. Of course, implementing an automated testing strategy comes at a cost. Weighing the benefits with the cost is critical and should not be missed in your organization or team.Don't forget to subscribe so you can be notified when Testing Series Part 2 on using Jest for unit testing in Angular is available for download!

Vor einiger Zeit fragten wir auf Twitter, wer von euch eigentlich Tests im Frontend schreibt. Die Antwort war mehr als verblüffend und somit geht's in der neusten Revision Working Draft mal wieder um …

Because of the high complexity and depth of this episode, we will share with you the episode outline and the topics discussed here as a reference.Episode Outline:What is unit testing?test for the smallest possible pieces of your program.كل حاجة فيها سليمة بس لوحدها - سلطان السكريWhy Unit TestingHelp the developer deeper understand the logic he/she is implementing.Help developer writes more modular, loosely coupled code.Make it faster to develop and debug. (You can fake all the possible scenarios and see how the test is responding to each)Find bugs early.Help with documenting the code you are doing.Help when it comes to refactoring.It helps to automate the development process and decrease deployment-related friction.Unit Testing Best Practices1- Identifying Units:When it comes to the unit you are testing, you need to answer three questions.a. What is the output of this unit?b. What helper functions that this unit is using to achieve that output?c. Are there any side effects resulting from this unit. (it modifies state variables outside its scope).2- Naming & DescriptionWhy? it makes the test easier to read and hence easier to figure out what went wrong.Describe & It. (This thing / should or does something)- The search function should return an array of strings matching the search keyword.- The search function should return an empty array when a keyword is not matching any.- throw an exception if the keyword is an empty string.3- Mocking & Stubs- The unit test is 50% mocking and 50% clean code.Check Martin Fowler's article in the for more depth in mocking Check the resources section. References:Martin Fowler's "Mocks Aren't Stubs".8 Benefits of Unit Testing.The testing introduction I wish I had.Rethinking Unit Test Assertions.Unit Tests: More Readable Describe/It Statements in Protractor/Jasmine. Episode Picks:Alfy: Dokkan Tech.Luay: Rich Dad, Poor Dad Book.

Stuff mentioned in this podcast:https://clubhouse.io37signals Employee handbook.The Famous git flow article for git workflow.https://keepachangelog.com/ for changelog tracking.A good article for git mentioning git rebase, squashing .. etc.Gitlab ChatOps.Health Check Monitoring Tools.Nightwatch: End-to-end testing, the easy way.Elk stack.LogRocket.Sentry.Prometheus.Grafana.Planning Poker for estimation.Architectural decision records.Cypress for E2E testing.Lighthouse.FastlaneToday Picks:Alfy: How to raise an adult book.Luay: Business wars podcast.

This week in the clubhouse, Stephen wants do more with less, Mark wants to do more with more, and Martha wants to do less to more."Because Internet: Understanding the New Rules of Language"  - Gretchen McCulloch, book"Your conference is too damn big"  - John Pavlus, Fast Company"The Game Design Studio on a Boat"  - Clinton Nguyen, ViceEvil Games Club co-host Dale is now tweeting for us! Follow us for behind-the-microphone goodness: @nicegamesclub. We're always trying to get feedback, but it's hard! So Dale is encouraging gamedevs to start using #FeedbackFriday on Twitter as a way for to get opinions from their peers on things they're working on. Try it out this Friday! Extra Modes 0:07:06 Mark LaCroixProduction"Assassin's Creed Isn't Necessarily Done With Multiplayer"  - Jordan Ramée, GameSpot"Why City Trial is the most memorable part of Kirby Air Ride"  - Chris Hovermale, Destructoid"Fortnite Battle Royale Took Two Months to Develop and Launch"  - Derek Nichols, GameRant"Riot got rid of League of Legends' URF mode because it made people stop playin… - Ali Jones, PCGamesN"Threading the Needle: The Making of Quake Team Fortress"  - David Craddock, Shacknews"The making of Gwent"  - Phil Savage, PC Gamer"Where Captain Toad: Treasure Tracker came from"  - Michael McWhertor, Polygon Unit Testing 0:41:31 Martha MegarryProgramming"Unit testing with Jasmine: The very basics"  - Aurel Kurtula, dev.toTesting Unity Projects  - ilkinulas, GitHubNUnit framework"Unit Testing Tutorial: What is, Types, Tools, EXAMPLE"  - Guru99, Guru99.com"What is Unit Testing, Why We Use It, and Sample Test Cases"  -  Lets Build That App, YouTubeTesting Computer Software, 2nd edition  - Cem Kaner, book"The 100% code coverage problem" - Jeroen Mols

Join Danny, Leon, and Amal for a discussion on unit testing modern web applications. Amal has recently taught a pilot testing workshop in Boston with Gleb from Cypress who was on the show last week. She is excited to evangelize the importance of unit testing. Unit tests are the vegetables of the JavaScript world - cooked properly, they are absolutely delicious, and you'll never want to stop eating them! Visit the website for This Week in Web, resources & more: https://thewebplatformpodcast.com/165-js-unit-testing-tools-best-practices   Follow The Web Platform podcast on Twitter for regular updates @TheWebPlatform.

Eric is back from the road trip. IoT, the gift that keeps on giving. Eric chats about hotel security cards. Jon channels Harry Potter with Obiliviate DNS. The Grand Canyon is really cool and Jon tries installing a garage door opener. Links: Grand Canyon - https://www.nps.gov/grca/index.htm Ski lift exposed to the internet - https://www.golem.de/news/patscherkofel-gondelbahn-mit-sicherheitsluecken-1804-133930.html Hotel key card security - https://wired.trib.al/RkHWQ0U The Hotel Hacker - https://www.wired.com/2017/08/the-hotel-hacker/ Oblivious DNS - https://www.techrepublic.com/article/oblivious-dns-could-protect-your-internet-traffic-against-snooping/ BGP Hijack - https://www.welivesecurity.com/2018/04/25/ethereum-cryptocurrency-wallets-raided/

In this episode I am joined by Ivan Nemytchenko from the open source company, GitLab. Here we take some time to explain what continuous integration and deployment is and how to get started with it in your development process. GitLab offers a free CI / CD solution called GitLab CI, but there are other solutions such as Jenkins and Travis CI as well. A writeup to this episode can be found via https://www.thepolyglotdeveloper.com/2016/11/tpdp-episode-11-continuous-integration-deployment-polyglot-developer/ If you have questions that you'd like answered in the next episode, visit https://www.thepolyglotdeveloper.com/podcast-questions and fill out the form.