 All right, let's do some Python on hardware news. This is from the ID4Daily newsletter, ID4Daily.com. We send it to you every single week. This is Python on hardware. Lady, Ada, you wanted to talk about, in addition to all the, go check out all the projects and everything, but in addition to the projects, the updates, the Python on hardware, you wanna talk about the automated hardware testing using PyTest this week. Yeah, this is cool. What is this? Why is this cool? Where are we? I think we're gonna log that. We're gonna log the line up here too. Yeah, it's, actually, I have to look into it because it's like it was in the newsletter and like, oh, I bookmarked it for later perusal. Because as we talked about in the show and tell, for Whipper Snapper data for now, yeah, we're starting to use this sort of mock Blinka to test the V2 of our Whipper Snapper API and also like verify the data is being sent correctly. And we don't want to use real hardware because we want to be able to run stuff in continuous integration, but maybe we do wanna sometimes run it on hardware, maybe one both either way. So what I thought was neat was Goliath who does hardware with CircuitPython and machine learning and IoT, they like have their own, I don't, I'm assuming that they worked on this or they have a tutorial on how to use PyTest. And I was like, oh, this is perfect because what we wanna do is once we start knocking out all the hardware interfaces for this like Blinka system for the fake hardware on Python, then we want to have like a way to quickly verify that when we add new systems to the protocol or like when we change the backend, we wanna quickly be able to run everything and make sure that like the regression still works like nothing has changed instead of waiting for customers to find out which is like kind of sad for the customer. Like they'll tell us and we'll fix it but we better if we caught it while we're writing the code. So I'm gonna check this out because we might be able to either run this on a Raspberry Pi with hardware or run it on GitHub Actions as we write the Blinka lock code and it will like maybe even test it against like Whipper Snapper, like we might have like a fake Whipper Snapper account that we have the GitHub's actions like talk to and then we can use REST to query what data got sent and like it will be like a nice round trip test. Cool. Basically it's like how to test hardware without testing hardware but testing the hardware that would have been tested. Anyways, I think you get to this level of attraction at some point. So I'm gonna read this article because Goliath has really good documentation. Okay. And so that's something that folks might be able to learn a little bit more and just from the newsletter, where would they see this in the Adafruit world? It works out. If it works out, you know, what you might see is especially Adafruit IO like you'll see this on the backend as we're doing the Whipper Snapper form which is public. You'll see the continuous integration running this. And also what might happen is if people are having issues with Adafruit IO we might ask them, hey, can you try this PyTest code on your hardware? So if they're running like Python hardware and say like, can you, you know, pip install PyTest and then run this PyTest suite and they will use the real hardware but tell us like where did it fail? Better than just saying like it doesn't work. Like we'll actually get like a proper report. Okay. And that's this week's Python on hardware. Yep. Again, don't forget it's on adafruitdaily.com.