Closed alfonsoegio closed 7 years ago
ok, thanks for the warning, tomorrow we'll discuss together with @dang03 the best way to set up the integration tests regarding both modules
Hi @jbonnet,
This integration test, int-gtkusr-keycloak
, is only and exclusively for son-gtkusr
and keycloak
in order to test the son-gtkusr
(Adapter) API and features with Keycloak, as son-gtkusr
can't work alone.
The test you are referring to is called int-usr-management
, which indeed will include son-gtkapi
and BSS
, and other components, to test end-to-end processes. However it is not finished yet because we first need to have son-gtkusr
and keycloak
working properly.
Hy, @alfonsoegio Please have in mind that the
son-gtkusr
should be invisible from the outside. What you should expect is the/api/v2/users/public-key
endpoint exposed in theson-gtkapi
. Integration tests should include theson-gtkapi
, not theson-gtkusr
, which will get tested in the end-to-end process. By the way, you already have that in the/api/v2/micro-services/public-key
endpoint, though in error: I've suggested theson-gtkusr
to return the public key in aJSON
object, instead of in pain text.