Ruby

Getting to the end of fixing the Standard Ruby Linter ToDo bug. In this video I refactor and remove duplicate code from a system tests that are similar. It goes well for the most part. The only hiccup is the trying to figure a way to run setup code once for all the tests in the file.

The system test is finally working!! I go over, again, why it’s important to make sure your tests fail. Now that the test is working I start refactoring it to remove duplicate code.

Spent longer then I would have thought trying to get a before setup method to work in MiniTest. During my investigation I think I got the JetBrains AI to suggest a fix for a MiniTest PR that was rejected which was interesting to see.

I, Chris, try to add a system test for the todo bug fix in episode 5 but run into some issues. I find out I stupidly hard coded the todo file name when he first added the ability to generate a todo file in Standard. When recording this video I think that is why his system test doesn’t work but upon re-watching this video I have my doubts. Only time will tell if my doubts are correct or not.

I add a unit test for the Standard Ruby linter bug fix done in the last episode. When adding the unit test I find out someone has improved the todo generation logic. Thank you. I also find a remove a redundant test.

Read about the bug being fixed here.

In this episode I implement a fix for the todo file generation bug in the Standard (Ruby linter) and do some manual testing. Also use ChatGPT to explain some code that GitHub Copilot generated.

Read about the bug being fixed here.

See the previous episode, number 4, where I create I duplicate the issue and come up with the fix possible fix.