Currently, testing certificate transparency as part of an end-to-end test requires configuring real logs and real certs, in such a way as to comply with whatever the current CT policies are in the tree. By virtue of needing to use real logs, inclusion testing also requires real STHs and real proofs.
To make it easier to maintain and understand the code, we may wish to explore either making it easier to use test-only logs (so that new and/or invalid answers can be generated on demand, as tests need), or to extract the necessary information from 'real' logs as appropriate.
Comment 1 by rsleevi@chromium.org
, May 3 2018