 So, hi everyone, I'm CMA, software testing engineer at the platform team, and I will give a quick update on what's happening on Moodle's testing and QA. We have been focused on our usual continuous integration work, managing and resolving PHP unit and we had failures. Additionally, we have been actively converting our QA tests into automated tests, like its ongoing efforts to improve the efficiency of our QA cycle. However, the highlight for this last sprint was the BeHAT performance improvements. More specifically, we added a new data generator to manage roles and permissions in Moodle. What this data generator does is it eliminates the need for manual steps. Search, login as admin, go to the defined roles page, change the permissions and save changes. But that's not part of the test, that's just to create the required data for the test. So, yeah, that's how, if you look in the left, that's how it was in the past. And now we have a new data generator, so you simply add this to this test and it will be a lot faster. We noticed in some tests it reduced it by minutes, the execution time just with that change. So, we have added a few other data generators, but that's the one, the most important one, but we have been adding like several ones. And of course, if you are working on your components and you come across a long and tedious test with lots of UI steps just to generate the required data for the test. So please report it on that MEGL and we will work on that to prioritize it and work on that. And finally, I'd like to take the opportunity to share a quick tip for my fellow HQ developers. Probably some people know, some people don't. That whenever you submit an MEGL for integration review or CI server has a job called Tobic that launches a build for each branch on that MEGL. However, in some cases that the changes might be super localized or sometimes you are adding a new test or a new function with each unit test. It's not required to run the whole switch. Sometimes you can just run the Tobic for that component and avoid that long execution running tests that are not related to your changes. So if you run a Tobic, I think we all, if you don't please send me a message and I will send you the link. If you run, if you launch a Tobic build on the MEGL before submitting for integration, it will, it won't automatically launch this whole build in the patch. Some cases it might make sense. Let's say you are changing a core function. It might make sense to run the whole switch, but most of the case, like if you are changing something forum or quiz or assignment, you can simply run the tests on that module and no need to run the whole thing. And that will save a lot of time and also resources in our CI server and everybody will thank you because yeah, we all get results faster. And yeah, that's all for now. Thank you for all your attention.