All E2E tests in IdentityHub are currently based on im-memory stores. This should be improved using the pattern we have in EDC, where there is an InMemory and a Postgres variant of the tests.
Which Areas Would Be Affected?
E2E tests
Why Is the Feature Desired?
test coverage. some errors only pop up when actual persistence is used.
Solution Proposal
use the pattern we have in EDC, using a base test class and nested subclasses
Feature Request
All E2E tests in IdentityHub are currently based on im-memory stores. This should be improved using the pattern we have in EDC, where there is an InMemory and a Postgres variant of the tests.
Which Areas Would Be Affected?
E2E tests
Why Is the Feature Desired?
test coverage. some errors only pop up when actual persistence is used.
Solution Proposal
use the pattern we have in EDC, using a base test class and nested subclasses