crispy VS GML-OOP

If you were interested in creating a future stable code base through the use of unit tests, you could look into implementing my framework Crispy.

I created a unit testing library called Crispy that you can check out.

The problem goes far beyond obscure bugs. Unless something has changed in recent months, then I can say with certainty that YoYo Games does not have Unit Tests for GameMaker. I know it because I made my own and in the process filled two pages of bug reports. They aren't even really complex, so most of them was related to basic functionality, because I essentially went through a list of functions and tried to get data from them. I would find functions that would straight-up never work or damage the resource they tried to affect instead of fulfilling its functionality. Before they move on to big projects like the ones they have announced, the QA needs to step up their game, because I am not into free labor anymore.

As for the performance impact, I note in the documentation that this is an additional layer of code in the core of its design and it will always take more time to execute. This would be the case for any GML library as a call of any function increases the execution time of the code it is responsible for and a potential user of such library has to approach it with that in mind. My current assumption is that it only is likely have a noticeable effect in huge or complicated projects or while misused and I will be testing this on my own work, as well be gathering feedback on the matter.