Home/ Questions/Q 616289
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T18:18:40+00:00

I am writing a fairly complicated machine learning program for my thesis in computer

  • 0

I am writing a fairly complicated machine learning program for my thesis in computer vision. It’s working fairly well, but I need to keep trying out new things out and adding new functionality. This is problematic because I sometimes introduce bugs when I am extending the code or trying to simplify an algorithm.

Clearly the correct thing to do is to add unit tests, but it is not clear how to do this. Many components of my program produce a somewhat subjective answer, and I cannot automate sanity checks.

For example, I had some code that approximated a curve with a lower-resolution curve, so that I could do computationally intensive work on the lower-resolution curve. I accidentally introduced a bug into this code, and only found it through a painstaking search when my the results of my entire program got slightly worse.

But, when I tried to write a unit-test for it, it was unclear what I should do. If I make a simple curve that has a clearly correct lower-resolution version, then I’m not really testing out everything that could go wrong. If I make a simple curve and then perturb the points slightly, my code starts producing different answers, even though this particular piece of code really seems to work fine now.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You may not appreciate the irony, but basically what you have there is legacy code: a chunk of software without any unit tests. Naturally you don’t know where to begin. So you may find it helpful to read up on handling legacy code.

    The definitive thought on this is Michael Feather’s book, Working Effectively with Legacy Code. There used to be a helpful summary​ of that on the ObjectMentor site, but alas the website has gone the way of the company. However WELC has left a legacy in reviews and other articles. Check them out (or just buy the book), although the key lessons are the ones which S.Lott and tvanfosson cover in their replies.

    2019 update: I have fixed the link to the WELC summary with a version from the Wayback Machine web archive (thanks @milia).

    Also – and despite knowing that answers which comprise mainly links to other sites are low quality answers 🙂 – here is a link to a new (2019 new) Google tutorial on Testing and Debugging ML code. I hope this will be of illumination to future Seekers who stumble across this answer.

    • 0