Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tests #591

Open
CosminPerRam opened this issue Jul 16, 2024 · 1 comment
Open

Add tests #591

CosminPerRam opened this issue Jul 16, 2024 · 1 comment

Comments

@CosminPerRam
Copy link
Member

In the past while I modifying the core code better and cleaner, I have changed stuff quite blindly, without fully knowing the complete image and possible side effects of what I have done, and I ended up spending tens of hours to modify bits of code.

Even top-level code can break very easily without tests (#584 is a perfect example), so going on forward we should prioritize making a tests suite for making sure we don't break anything via possible rewrites (GameDig 6 will be all about rewriting old code).

@CosminPerRam CosminPerRam moved this to Backlog in GameDig 6 Jul 21, 2024
@CosminPerRam
Copy link
Member Author

CosminPerRam commented Aug 20, 2024

Here is yet (unfortunately) another example of something that could have been avoided: #611

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant