This article from @bert_hubert spells out the principles of sustainable software development really, really well.

If you have a decision that is in any way a close call, I say go with the choice that embodies these principles.

Your future team (which might include you) will thank you.

https://berthub.eu/articles/posts/on-long-term-software-development/

On Long Term Software Development - Bert Hubert's writings

Recently the Dutch Electoral Board (where I am also a very part time advisor) invited me to do a talk reflecting on their open source Abacus vote tabulation software. Much software is now provided as a service, and is typically deployed continuously (CD, continuous deployment), surrounded by enough automated testing (CI, continuous integration) that we can be reasonably sure that a new revision is likely to at least work to some extent.

Bert Hubert's writings

@elizayer @bert_hubert Thanks for sharing!

Ideally the tests should be treated as part of the documentation since they show how things are supposed to work.
The files should follow a clear structure, be readable and entail descriptions.

Code and dependencies for the tests should be reviewed on a regular basis so that time passing doesn't become an additonal obstacle.