Some other things he's been working on Vladimir. The stage is yours. Thank you. Chris and I apologize. My my zoom says my internet connection is unstable. Sonic I'll try to make the best out of it.

Let me share my screen: are you able to see my screen?

Yep? Oh great, okay, so my brief. A segment is about running tests for modified files first, so what is the problem? Say, I'm a developer in a large project and it's ci testing stage takes forever and I just want to see the unit tests only for my changes. So what are my options? I can wait. 45 minutes just to see my unit tests fail or I can skip automated test development altogether. To avoid the failure. So I, don't always taste my code, but when I do I, do it in production.

What is the solution? Then? Ok, so 13 one comes with the ability to run tests for modified files first. So how that's a good question? There is a gem called test file finder. It accepts a list of modified files and returns a list of specs or tests that it thinks are relevant to the input files and then by default. It runs this part in the pre stage of the CLABSI ICD pipeline ahead of anything else.

So this is what it looks like a spec config includes the pretty much. This is the standard definition of a spec test it triggers when med request is submitted, then it installs dependencies runs tests and then in CI CD. You include the template that is fail fast, get lap, CI llamo, then, in that file it it specifies the pre stage that runs before anything else, and it looks for changed RB files and then it installs the test file finder gem.

Then, if there are any changes in IB files, it runs the tests applicable to those recent changes. First, that way, developer is able to see what their tests are like before the rest of the CI CD pipeline runs. So the link contains some of the requirements for the template and that's pretty much it slow and steady wins the race. False fast, always wins the race. Thank you. Everyone.