We want to exercise the ocsp-updater in integration tests, and ensure that when OCSP responses are re-signed (after the initial issuance signature or a signature performed on revocation), they have the correct certStatus and revocationReason. To do this, we need to simulate the passage of time after a revocation happens. We can probably combine this with the setup_twenty_days_ago tooling, by issuing and then revoking a certificate in the past, then checking it in the present. The integration test will need to check the ThisUpdate field to and loop until it is updated, to ensure that the ocsp-updater has had at least one successful run before we verify its output.
We want to exercise the ocsp-updater in integration tests, and ensure that when OCSP responses are re-signed (after the initial issuance signature or a signature performed on revocation), they have the correct certStatus and revocationReason. To do this, we need to simulate the passage of time after a revocation happens. We can probably combine this with the setup_twenty_days_ago tooling, by issuing and then revoking a certificate in the past, then checking it in the present. The integration test will need to check the ThisUpdate field to and loop until it is updated, to ensure that the ocsp-updater has had at least one successful run before we verify its output.