Some sudden program ideas (modular processing)

Today I am testing the algorithm program I have written , But it takes a long time for the whole program to run smoothly （10~30 minute ）.
I'm thinking about how to test a certain part of the program , That is, the one with problems .

1. Step by step debugging

Single step debugging is really good , It can check the real-time data running to a certain row , But if my program is in Posterior half fault If something goes wrong , Don't I have to wait until the program runs later to debug ？ This is obviously inefficient for such a long program （ Don't ask me how I know ）

2. Program modularization （ High cohesion and low coupling ）

In fact, my algorithm program can be roughly divided into two modules: operation and drawing , But for now , Drawing depends on the result of the operation , Call the result data to run , The coupling of writing is too high , The maintenance cost and readability of the program have become lower . I should Implementation allows each module to complete specific sub functions as independently as possible .
Let the operation module generate a Drawing needs csv file , Then draw by reading this file . Instead of directly calling the result data .
In this way, when the operation module outputs normally , Just test the problematic drawing module .