Podcasts about writing tests

Keri Olson (@ksolson20, VP AI for Code at @IBM) talks about coding assistants across the software development lifecycle, the future of agents, and domain-specific assistants.SHOW: 869SHOW TRANSCRIPT: The Cloudcast #869 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET CLOUD NEWS OF THE WEEK: http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT OUR OTHER PODCAST:  "CLOUDCAST BASICS" SHOW SPONSOR:While data may be shaping our world, Data Citizens Dialogues is shaping the conversationFollow Data Citizens Dialogues on Apple, Spotify, YouTube, or wherever you get your podcastsSHOW NOTES:IBM Watsonx Code Assistant (homepage)IBM Watsonx Code Assistant for Ansible Lightspeed (homepage)IBM Watsonx Code Assistant for Z (homepage)Topic 1 - Welcome to the show. Tell us about your background, and then give us a little bit of background on where you focus your time at IBM these days?Topic 2 - Developer code assistants have become one of the most popular areas of GenAI usage. At a high level, how mature are the technologies that augment developers today? Topic 3 - Software development has an entire lifecycle (Generate, Complete, Explain, Test, Transform, Document). It's easy for developers to just plug in a service, but is that often the most effective way to start using GenAI in the software development lifecycle? Topic 4 - Software developers are notoriously picky about what tools they use and how they use them. GenAI doesn't “guarantee” outputs. Are there concerns that if different developers or groups use different coding assistants, that it could create more challenges than it helps? Topic 5 - What is a holistic way to think about code assistants? How much should be actively engaged with developers, how much should be behind the scenes, how much will be automated or agentic in the future? Topic 6 - In the past, we essentially had “real developers” (people who wrote code) and things like Low-Code for “citizen developers” on process tasks. Do you expect to see code assistants bringing more powerful skills to people that previously hadn't identified as a real developer? (e.g. the great idea on a napkin that turns into a mobile app)FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

Knowing how to write unit tests will make you a better, more hire-able developer. Few bootcamps teach this for some reason and since I like you, I made a FREE Unit Testing guide you can grab here.  Unit Testing Pro.Having trouble? Shoot me an email at brian@parsity.ioShameless Plugs

We always write tests, and can't imagine working without them. But is there ever a time where it might make sense to delay writing some tests until later in the project? Let us tell you a story about a recent project where we made that decision.(00:00) - Our secret podcast agenda (01:00) - Project setup (02:30) - Tests are good, but they do add time (03:15) - Some ambiguity on "is this what the user needs/wants?" (06:00) - Discussing the decision to delay tests as a team (07:15) - Conclusion - it's the audience, not the timeline (08:10) - Side benefit of knowledge sharing (09:15) - Silly bit Become a more confident Laravel developer. Sign up for practical tips at masteringlaravel.io

What happens when a prospective client asks you to write a trial post for free? What about an unpaid test? Are there circumstances where doing work that's unpaid makes sense or is this always a big NO? In this episode, we talk about writing tests, trial posts, and when it might make sense to write for free (or not!).

Mike Bland is a software instigator - he helped drive adoption of automated testing at Google, and the Quality Culture Initiative at Apple.Apple Podcasts | Spotify | Google PodcastsMike's blog was instrumental towards my decision to pick a job in developer productivity/platform engineering. We talk about the Rainbow of Death - the idea of driving cultural change in large engineering organizations - one of the key challenges of platform engineering teams. And we deep dive into the value and common pushbacks against automated testing. Highlights (GPT-3 generated)[0:00 - 0:29] Welcome[0:29 - 0:38] Explanation of Rainbow of Death [0:38 - 0:52] Story of Testing Grouplet at Google[0:52 - 5:52] Benefits of Writing Blogs and Engineering Culture Change [5:52 - 6:48] Impact of Mike's Blog[6:48 - 7:45] Automated Testing at Scale [7:45 - 8:10] "I'm a Snowflake" Mentality [8:10 - 8:59] Instigator Theory and Crossing the Chasm Model [8:59 - 9:55] Discussion of Dependency Injection and Functional Decomposition[9:55 - 16:19] Discussion of Testing and Testable Code [16:19 - 24:30] Impact of Organizational and Cultural Change on Writing Tests [24:30 - 26:04] Instigator Theory [26:04 - 32:47] Strategies for Leaders to Foster and Support Testing [32:47 - 38:50] Role of Leadership in Promoting Testing [38:50 - 43:29] Philosophical Implications of Testing Practices This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.softwareatscale.dev

Today's episode is sponsored by Codiga, a smart coding assistant and automated code review platform.Links:For a chance to win the “Effective Software Testing” book, like and retweet today's episodeEffective Software Testing – The BookFlaky Tests blog post by MauricioMauricio's newsletterThe art of testing less – How Microsoft copes with flaky testsSubscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Video content can be found here: https://www.youtube.com/channel/UC0BAd8tPlDqFvDYBemHcQPQ/

Is it possible to predict who will develop Alzheimer's disease simply by looking at writing patterns years before there are symptoms? We asked that question to Guillermo Cecchi, principal researcher at IBM Research and lead scientist on their Alzheimer's prediction research. You'll have to listen to the episode for the answer, but it's worth the listen. Guillermo discusses how IBM researchers trained artificial intelligence to pick up hints of changes in language ahead of the onset of neurological diseases – and it's just the beginning.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this lesson we discuss how the IELTS exam day went, focusing specifically on the IELTS speaking and writing tests. We discuss a strange experience in the speaking exam and how to best to manage your time in IELTS Writing Task 1 and Writing Task 2.

Hey there friends. So today I'm going to talk about testing and the users of your code and how you should think about like how what do I test? So pretty common question. And the answer is basically you take a unit of code that you want to have tested that could be a single function or it could be an entire application. It really just comes down to what you want to get confidence in. Most of us are probably in the camp of like I just want my to be sure that my entire application works and that's great. And that'sTypically where where I'm thinking and in my own mindset sometimes though, it's hard to accomplish the thing that you're trying to test from a whole application perspective and that's when you go to lower level forms of testing but that's not what I'm going to talk about today. So once you've identified the unit of code that you want to have tested the next thing you need to do is think about who the users of that code are. So if we're talking about a react component, for example, then you're going to have two users of your code. And in fact most of the time,You're going to have two users of your code, unless you're doing full-on and to end testing with nothing mocked. And the two users are the end user who's going to be interacting with that code and the developer user who's going to be making network requests to your API handler or maybe they're calling into your function or their rendering your component, whatever it is. So you have those two two users of your code. And so then as you're thinking about what you know, what you should write.For your test you're going to say okay well so what is the what do mind users do What are the use cases that this code supports and how do I make like what are of those use cases what are the most important things that I ensured don't break? Because they're like for an application there are some parts of the application that matter more than others. And so you're going to identify all the use cases that you want to support and kind of sort them in your mind or maybe even write it down. The order of priority for those things. So once you have decided what use cases you want to support you just go one.By one to write a test for that particular use case. And the way that you write that is you could even write this in code comments or something before you write the test you just say how do if I were a user manually testing this whether you're the end user or the developer user probably both how would I interact with this component to make it do the thing that I'm trying to support? How do I show that use case in my test? And then you write code to do that. I hope that's helpful and I hope you have a splendid day. Good luck.And writing those tests get yourself a lot of confidence and we'll see you around.

Production team:Host & Producer: Maria XenidouIntroduction Voice: David Bourne  Contact us:impactlearningpodcast(at)gmail.com  Music credits:Like Lee performed by The Mini VandalsTransition sounds: Swamp Walks performed by Jingle Punks Where to find more about Christine Oliver:LinkedInTwitter Mentioned in this episode:Classroom, IncRead to Lead GamesLewis W. BernardThe Urban Assembly Listen to this episode and explore: Christina’s childhood: playing hide & seek and experiencing the joy of learning (4:50)How her parents inspired Christina’s interest in education and reading (7:00)Her love for history and humanity and her preference for hands-on learning in biology (8:00)The person who inspired Christina to become a teacher (9:05)What Christina learned about herself in her first job at a rifle club at the age of 13 (10:00)Why Christina delayed her teaching career and got involved in politics at the NY State Assembly (12:00)The role of representation in politics and how power can often lead to corruption (14:00)How working at the NY State Governor’s office and visiting NYC led Christina to become a teacher in the Bronx (15:12)Why teaching is the hardest job on the planet and why Christina loved it (16:45)How life took Christina out of teaching when family illness sent her back to NY state (17:40)How Christina started working on the intersection of politics and education in Washington, DC (18:25)Why Christina decided to pursue her Masters in Education at Columbia SIPA in NYC (19:15)How Christina’s interest in education reform led her to join the Urban Assembly (20:00)Her decision to join Classroom, Inc and her current role as Executive Director (22:45)The vision and mission of Classroom, Inc and their Read to Lead learning games platform (24:25)How game-based learning helps bridge the skills gap between middle school and career (24:58)How middle schoolers get exposure to over 30 different careers while building literacy skills (27:52)What the Read to Lead games reminded Maria of during her former corporate career (31:04)How the Read to Lead games, curriculum and resources develop and empower teachers to become more effective educators (32:45)How adaptive learning is built in the Read to Lead games design to help struggling readers (35:70)The three main Read to Lead learning games (39:65)How the students build skills and confidence to be the boss at work (41:75)The mission of Read to Lead: serving communities that lack resources and access to education (45:00)How educators can access the free Read to Lead games, curriculum and resources (47:70)What teachers love about Read to Lead: its unique value and impact on society (49:98)What Christina wants to leave her mark on during her lifetime and Maria’s reflection (54:64)

In this episode I'm joined by repeat guest, and awesome developer, Corbin Crutchley from Unicorn Utterances. The topic of this episode is on testing, and I'm not talking about taking exams, I'm talking about writing tests in your development projects to produce much better final products. If you've ever been curious about the differences between unit tests, integration tests, end to end tests, and all of the other possible types of tests that might exist, this episode is for you. It doesn't matter if you're a new developer, a casual developer, or expert developer, knowing how to write tests will greatly benefit your career. A brief writeup to this episode can be found via https://www.thepolyglotdeveloper.com/2020/06/tpdp-e37-writing-tests-development-project/

01:19 – Kent’s Superpower: Putting Things Together That Don’t Necessarily Go Together Surfaces and Essences: Analogy as the Fuel and Fire of Thinking by Douglas Hofstadter and Emmanuel Sander (https://www.amazon.com/gp/product/0465018475/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=therubyrep-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=0465018475&linkId=6b695b9a8370a14771836fb3671d11e5) 04:01 – Metaphors in Software Development 07:32 – Writing Tests and Keeping a Journal @jessitron (https://twitter.com/jessitron/status/938122417548881920?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E938122417548881920&ref_url=https%3A%2F%2Fwww.greaterthancode.com%2F2017%2F12%2F27%2F060-coping-with-complexity-with-kent-beck%2F) The unit/integration distinction confuses me. I test at the level of, “Here’s a thought I need to capture.” @KentBeck on @greaterthancode 10:58 – Complexity Partitioning One Bite At A Time: Partitioning Complexity (https://www.facebook.com/notes/kent-beck/one-bite-at-a-time-partitioning-complexity/1716882961677894/) Kent’s musings on the topic of unit versus integration testing after the show. (https://www.facebook.com/notes/kent-beck/unit-tests/1726369154062608/) 21:59 – The Way Systems Change Over Time as an Important Part of How We Design Software 27:20 – Changing Culture Vs Code and Storytelling and Succession Reflections: Jamey: Thinking about the reasons why we do things. Rein: How computer systems are beginning to take on the complexity of biological systems. Coraline: The concept of lumpers vs splitters. Sam: How strategies for dealing with complexity don’t just have to be about the problem itself, they can be about the emotional response of the programmer who has to get some work done. Jessica: The for-allers vs the for-eachers; universalist vs existentialist. Kent: Not being bothered by culture change and helping people feel the same. 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: Kent Beck.

An answer for a question on my AMA (https://github.com/kentcdodds/ama/issues/336). Links: - Testing JavaScript Applications Workshop (http://kcd.im/fm-testing) - Here's the barebones example (https://github.com/kentcdodds/testing-workshop/blob/master/other/start.html)

A brief update.

00:43 - Scott Moss Introduction Twitter GitHub Udacity @udacity Hack Reactor Angular Class @angularclass 01:55 - Scott’s Programming Background 04:11 - Working with Lukas 05:04 - Angular and ES6 (ECMAScript) John Papa's Angular Style Guide 06:11 - Subclassing a Directive Classical Inheritance DDO (Directive Definition Object)    08:58 - TypeScript     Transpiling traceur-compiler babel Differences and Definitions: traceur, babel, TypeScript Learn about TypeScript 1.5 here and get it here [Pluralsight] John Papa and Dan Wahlin: TypeScript Fundamentals Types Have Value 19:06 - How should people use a transpiler in a real application? webpack gulp.js jspm 21:07 - systemjs 21:53 - Build Systems vs Package Managers     24:15 - Writing Tests in ES6 26:03 - Debugging 28:20 - How coding in ES6 has changed Scott’s style of building Angular 1 apps 30:19 - Modularity Arrow Functions 33:07 - ES5 with Angular 2?? 37:31 - Good Example of Using ES6 with Angular GoCardless GoCardless Angular Style Guide 39:21 - Learning New Material and Using ES6 Picks Learn about TypeScript 1.5 (Ward) The Effective Engineer by Edmond Lau (Lukas) Isar Raw Canvas Backpack (Lukas) INcontroL (Joe) John’s Daughter (John) Angular U (John) The Imitation Game (Katya) Treeline (Scott) Interstellar (Scott)           

00:43 - Scott Moss Introduction Twitter GitHub Udacity @udacity Hack Reactor Angular Class @angularclass 01:55 - Scott’s Programming Background 04:11 - Working with Lukas 05:04 - Angular and ES6 (ECMAScript) John Papa's Angular Style Guide 06:11 - Subclassing a Directive Classical Inheritance DDO (Directive Definition Object)    08:58 - TypeScript     Transpiling traceur-compiler babel Differences and Definitions: traceur, babel, TypeScript Learn about TypeScript 1.5 here and get it here [Pluralsight] John Papa and Dan Wahlin: TypeScript Fundamentals Types Have Value 19:06 - How should people use a transpiler in a real application? webpack gulp.js jspm 21:07 - systemjs 21:53 - Build Systems vs Package Managers     24:15 - Writing Tests in ES6 26:03 - Debugging 28:20 - How coding in ES6 has changed Scott’s style of building Angular 1 apps 30:19 - Modularity Arrow Functions 33:07 - ES5 with Angular 2?? 37:31 - Good Example of Using ES6 with Angular GoCardless GoCardless Angular Style Guide 39:21 - Learning New Material and Using ES6 Picks Learn about TypeScript 1.5 (Ward) The Effective Engineer by Edmond Lau (Lukas) Isar Raw Canvas Backpack (Lukas) INcontroL (Joe) John’s Daughter (John) Angular U (John) The Imitation Game (Katya) Treeline (Scott) Interstellar (Scott)           

00:43 - Scott Moss Introduction Twitter GitHub Udacity @udacity Hack Reactor Angular Class @angularclass 01:55 - Scott’s Programming Background 04:11 - Working with Lukas 05:04 - Angular and ES6 (ECMAScript) John Papa's Angular Style Guide 06:11 - Subclassing a Directive Classical Inheritance DDO (Directive Definition Object)    08:58 - TypeScript     Transpiling traceur-compiler babel Differences and Definitions: traceur, babel, TypeScript Learn about TypeScript 1.5 here and get it here [Pluralsight] John Papa and Dan Wahlin: TypeScript Fundamentals Types Have Value 19:06 - How should people use a transpiler in a real application? webpack gulp.js jspm 21:07 - systemjs 21:53 - Build Systems vs Package Managers     24:15 - Writing Tests in ES6 26:03 - Debugging 28:20 - How coding in ES6 has changed Scott’s style of building Angular 1 apps 30:19 - Modularity Arrow Functions 33:07 - ES5 with Angular 2?? 37:31 - Good Example of Using ES6 with Angular GoCardless GoCardless Angular Style Guide 39:21 - Learning New Material and Using ES6 Picks Learn about TypeScript 1.5 (Ward) The Effective Engineer by Edmond Lau (Lukas) Isar Raw Canvas Backpack (Lukas) INcontroL (Joe) John’s Daughter (John) Angular U (John) The Imitation Game (Katya) Treeline (Scott) Interstellar (Scott)           

Check out RailsClips on Kickstarter!!   00:58 - Andres Dominguez Introduction Twitter GitHub Blog Google: New York 01:47 - protractor Selenium WebDriver WebDriverJs JavaScript Jabber Episode #106: Protractor with Julie Ralph Julie Ralph 03:50 - elementor [YouTube] Elementor, an improved element explorer for protractor elementexplorer [YouTube] Protractor's element explorer IDEs WebStorm IntelliJ IDEA 09:54 - Use Outside of Angular 10:37 - The Name: “Elementor” 11:11 - Conception => Production Writing Tests Text Editors Sublime vim 12:42 - Implementing Elementor / Workflow TDD (Test-driven Development) 14:39 - Testing a Non-Angular Website 15:31 - Installing the Elementor Chrome Extention Google Developer Tools 18:45 - Running in Emacs 19:47 - Plugins (egghead.io)     sjump ddescriber 20:47 - Debugging Picks Open Space Events and Conferences (Joe) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck) DevDocs (Andres)  

Check out RailsClips on Kickstarter!!   00:58 - Andres Dominguez Introduction Twitter GitHub Blog Google: New York 01:47 - protractor Selenium WebDriver WebDriverJs JavaScript Jabber Episode #106: Protractor with Julie Ralph Julie Ralph 03:50 - elementor [YouTube] Elementor, an improved element explorer for protractor elementexplorer [YouTube] Protractor's element explorer IDEs WebStorm IntelliJ IDEA 09:54 - Use Outside of Angular 10:37 - The Name: “Elementor” 11:11 - Conception => Production Writing Tests Text Editors Sublime vim 12:42 - Implementing Elementor / Workflow TDD (Test-driven Development) 14:39 - Testing a Non-Angular Website 15:31 - Installing the Elementor Chrome Extention Google Developer Tools 18:45 - Running in Emacs 19:47 - Plugins (egghead.io)     sjump ddescriber 20:47 - Debugging Picks Open Space Events and Conferences (Joe) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck) DevDocs (Andres)  

Check out RailsClips on Kickstarter!!   00:58 - Andres Dominguez Introduction Twitter GitHub Blog Google: New York 01:47 - protractor Selenium WebDriver WebDriverJs JavaScript Jabber Episode #106: Protractor with Julie Ralph Julie Ralph 03:50 - elementor [YouTube] Elementor, an improved element explorer for protractor elementexplorer [YouTube] Protractor's element explorer IDEs WebStorm IntelliJ IDEA 09:54 - Use Outside of Angular 10:37 - The Name: “Elementor” 11:11 - Conception => Production Writing Tests Text Editors Sublime vim 12:42 - Implementing Elementor / Workflow TDD (Test-driven Development) 14:39 - Testing a Non-Angular Website 15:31 - Installing the Elementor Chrome Extention Google Developer Tools 18:45 - Running in Emacs 19:47 - Plugins (egghead.io)     sjump ddescriber 20:47 - Debugging Picks Open Space Events and Conferences (Joe) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck) DevDocs (Andres)  

Ben Orenstein is joined by Gordon Fontenot and Matt Mongeau, two thoughtbot developers, to discuss iOS development using both Objective-C and RubyMotion. Ben, Matt, and Gordon talk about the differences between the two platforms for iOS development, testing in iOS development, the difficulty in it, and the ways to do it. They also make they're recommendations for getting started with iOS development, and discuss iOS apps they like, designing iOS applications, the iOS release cycle, and much more. RubyMotion LLVM CoffeeScript Bacon, a small RSpec clone Writing Tests for RubyMotion Apps Joel on Software, "Back to Basics" The LLDB Debugger rubymotion-tutorial.com RubyMotion, by Clay Allsop Test-Driven iOS Development All the C You Need to Know Fantastical for iPhone UIAppearance CocoaPods Follow @thoughtbot, @halogenandtoast, @gfontenot, and @r00k on twitter.

Writing Code is the Easy Part is the new slogan for the website. It basically boils down to the fact that putting up syntacticly correct code is the simplest part of coding. More difficult is solving problems and all of the other things that come with having a job or working for clients. Here are some of the things that I listed as the harder parts of coding: Legacy Code Readability Testability Best Practices Writing Tests Team Dynamics Customer Communication Translating Behavior into Code Data Integrity Security Maintainability Systems Integration Server Technologies Databases Finding a Job Hiring and Firing Working on Boring stuff Job Fulfillment Here are affiliate links to some of the books that I mentioned: Refactoring: Improving the Design of Existing Code Design Patterns: Elements of Reusable Object-Oriented Software Code Complete: A Practical Handbook of Software Construction The Pragmatic Programmer: From Journeyman to Master The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) Here are the links to the podcast episodes by: Chad Fowler (Part 1, Part 2) Dave Thomas (Part 1, Part 2) Finally, I would really appreciate a $5 donation to help me get to RubyConf. Download this Episode

Interview with Xiaoming Xi on automated scoring of speaking and writing tests.