@patrickyevsukov As I'm updating the site, I've had to work around the repo structure a bit to fix things up for automation consistency while doing my best to leave the repo unaffected (like normalizing to lowercase which is something I'm glad I've picked up and will definitely use in the future), so I've gotten pretty familiar with patterns in the files and structure.

A lot of people didn't include test files in the beginnings of the repo, less so when it started growing but some still missed them, and some people still are missing them in new pull requests, so I vote that it should be optional.

I am planning on making use of implementations that have tests, on the site, but my automation scripts should be able to reliably detect and mark whether or not they do, so it shouldn't be problematic to make it optional.