Closed jamshale closed 2 months ago
The askar-anoncreds profile should have a scenario for the new scenario testing that at least tests basic issuance and revocation and notification testing, like the current https://github.com/hyperledger/aries-cloudagent-python/blob/main/scenarios/examples/presenting_revoked_credential/example.py scenario test.
A scenario testing an actual upgrade for single tenancy from the askar to askar-anoncreds profiles would also be good. It's currently tested for multitenancy with the BDD style tests.
This comes up because the revocation notifications weren't working correctly with both publish and notify options. See https://github.com/hyperledger/aries-cloudagent-python/pull/3226#pullrequestreview-2297830747
Closing this as the problem scenario is now tested. Will create new tickets for additional testing.
The askar-anoncreds profile should have a scenario for the new scenario testing that at least tests basic issuance and revocation and notification testing, like the current https://github.com/hyperledger/aries-cloudagent-python/blob/main/scenarios/examples/presenting_revoked_credential/example.py scenario test.
A scenario testing an actual upgrade for single tenancy from the askar to askar-anoncreds profiles would also be good. It's currently tested for multitenancy with the BDD style tests.
This comes up because the revocation notifications weren't working correctly with both publish and notify options. See https://github.com/hyperledger/aries-cloudagent-python/pull/3226#pullrequestreview-2297830747