I have a problem with testing a complex strategy that does a lot of calculation when started that any attempt to stop the strategy does not succeed until the calculation is completed. This is surprising to me, as I would have thought the system would be written in a way that permits a calculation to be interrupted. Since it is not, the question is how can code be written to specifically allow a strategy to be stopped during a calculation? The sort of thing I am imagining is a line of code to be executed at reasonably spaced intervals that will permit the strategy to be stopped even if there is more calculation to be done?

Any ideas? Should be of quite broad interest.

In general this bigger workload needs to be split into several smaller pieces. Smaller work items could be iterated in a loop. On each iteration we would check if the work needs to be stopped and break out of the loop when needed.