How to efficiently iterate and validate geometric algorithms when adding or modifying them in OCC (Open CASCADE Technology)?

[Chuanzhenqi]

My starting point is that I’m not yet familiar with the codebase of this project.

I’d like to modify or optimize a specific geometric algorithm without touching other parts of the code.

The key challenge with large-scale projects like OCC is:

How can I flexibly and efficiently integrate a new algorithm module—or improve an existing one—while keeping the workflow simple and fast, so that the build process doesn’t become a time bottleneck?

My current idea for an automated workflow (taking modification of an existing geometric algorithm module as an example) is:

• Modify the source code within the original module.
• Compile only this changed part (avoid rebuilding the entire project to save time).
• Automatically install the resulting shared library (e.g., .so or .dll) into the target directory.
• Use test cases in the frontend to call the relevant APIs and verify the correctness and stability of the updated algorithm.
  However, I’m unsure:

Is this workflow reasonable?
Are there important aspects I’ve overlooked?
How do experienced developers typically validate, test, and refine specific algorithms in large codebases like OCC?
I’d especially appreciate insights on how to streamline this process into an efficient, iterative workflow that supports rapid experimentation and optimization.