 I'm Simi Lamez, software test engineer at the platform team, and I will be giving a quick update on the QA and testing side of things. So in the automated testing development, I have started looking at handling emails with Behatch. So the idea is that we can send an email to Moodle, to capture that using Behatch and validate the content. Sometimes click on a link that will confirm an account. For example, clear the inbox and mark messages as read and read. So that's a really cool thing that will help us to get rid of some QA tests in the long term as well. We also have been fixing some CI failures and converting manual steps to data generators. That's pretty much being done by Angelia. On the QA side of things, we've also have been converting QA tests to Behatch and also reviewing the existing tests to verify which ones are already covered by Behatch in some way. So by doing that, we managed to remove 37 tests from the matrix. So just for reference last QA cycle, we started with 615 tests, and now we are at 566, and with the ongoing conversions, that number will go down a little bit. And a heads up that our QA cycle is not that far away. It's less than a month away, so start preparing yourselves and organizing with the teams. One important thing is to verify if there are projects that will have work landed after the QA cycle started. So we can put those issues on hold. And yeah, at some point, I will start sending the links to the dashboards with the failures. So each tech chain can, we have a more organized way to handle the QA test fails. And yeah, that's pretty much me on the QA and testing side of things. Anyone have any questions?