I have thought about why it is much harder to follow the general best practice of Unity Tests + Automated Tests we find in web development and I think it is bec

I have thought about why it is much harder to follow the general best practice of Unity Tests + Automated Tests we find in web development and I think it is because the amount of "state" a video game has. In the web we have our cursor and it clicks on an element. In video game design the character can widely vary when it interacts with an element such as a "door". The classic "why doors are hard" might explain why having a "regression suite for happy paths" might be near-impossible. Though that the core reason for using the Entity, Component, Systems (ECS) in their coming Data Oriented Technology Stack (DOTS) it does help create far more maintainable code. https://www.vox.com/videos/22661048/video-game-development-door-difficulty-design https://www.vox.com/videos/22661048/video-game-development-d... https://unity.com/dots https://unity.com/dots