Say you have a library in which path explosion occurs. Further, say that you aren't interested in the paths of that library per se, but need the library captured so as to keep return values symbolic.
One solution is to designate that library as undesirable for testing by increasing the weight of code from that library. This weight could be specified as 2x, 3x, etc. the normal weight (1x). That way, paths through that library would be demoted, and paths that leave the library the soonest would be preferred.
This should be rather simple to combine with the "weighted" strategy. Just initialize the weight of each node in the execution graph to be the one specified.
Say you have a library in which path explosion occurs. Further, say that you aren't interested in the paths of that library per se, but need the library captured so as to keep return values symbolic.
One solution is to designate that library as undesirable for testing by increasing the weight of code from that library. This weight could be specified as 2x, 3x, etc. the normal weight (1x). That way, paths through that library would be demoted, and paths that leave the library the soonest would be preferred.
This should be rather simple to combine with the "weighted" strategy. Just initialize the weight of each node in the execution graph to be the one specified.