what we did, with tessent/fastscan, just load the netlist as usually, and there is a command to analyze the compression ratio optimum for the design.
based on that you could generate the kompression engine.
The compression ratio could be just to reach a ATE time, without looking to be at the "optimum" point.
for secure way (in case kompression issue) and design constraint, in a previous design, we have four scan modes:
1- 2 scan chains without compression (bypass mode)
2- 2 scan chains with compression with 384 internal scan chains
3- 8 scan chains without compression (bypass mode)
4- 8 scan chains with compresion with 384 internal scan chains