Create standalone test cases by automatic extraction of context data
When a problem is encountered in a real operational context, it is
difficult to extract minimal context
data to create standalone test cases. The whole Digital Elevation Model is required, which
implies providing both the tile updater implementation and the data files, the whole orbit
and attitude is required ...
As a consequence, it is often necessary to debug the Rugged library
right from within the
full operational system, which is cumbersome and requires the Rugged team to have access to
It would be desirable to have a way to dump minimal data context on the
when an error is triggered (either programmatically or from a single run under a debugger),
and to be able to send this minimal dataset to the Rugged team where it could be used to
reproduce the same call and debug Rugged itself, without any access to the operational
system and its data.
The minimal context data would contain a subset of the full data:
position, attitude and
more importantly only the few DEM cells data for the points used in the failing call,
not the full call data. This should be a few tens of cells, not millions of data points.
These important data points are the ones accessed directly by the intersection algorithm
as well as the min and max elevation points for the associated sub-tiles.
(from redmine: issue id 188, created on 2015-01-28, closed on 2016-02-10)