are there any books/websites which focus on testing and structuring of research code? I feel code that is written for research purposes has to be approached differently, than let's say a web application.
In company where I work, research code at some point actually becomes our production code and I'm kind of scared that there is no Q/A process established. I mean multiple people check it along the way, but given nobody knows exactly what the output looks like, I'd say chances are that there is a lot of bugs hidden in our codebase.
How would you generally test such code? In the same way as other web/desktop applications? I feel like approaches which normally work in dev (i.e. TDD) fall short when we're talking about research, where you do not know what the end state is. But at the same time, having no tests is also foolish and short-sighted.