Testing with mocking libraries?
by Stian Thorgersen
At the moment our testing strategy is only with functional or integration
level tests. Both with the full server up and running and primarily testing
through public APIs.
Now here comes the question should we also allow testing through a mocking
library like Mockito?
In general I'm against mocking libraries. At best you end up with something
that may work, but you're not guaranteed that it actually works. They also
have a very big maintenance cost when any changes are made to the codebase.
However, take a look at https://github.com/keycloak/keycloak/pull/5215 for
example. It is a contribution to add support for the hd param to the Google
login. Not sure how else we could test this without a mocking library.
6 years, 1 month
Looking for implementation assistance
by iain.clarke＠empala.com
We need help!
We are creating a new Node.JS platform and looking to use Keycloak. We have
a POC up and running, but I'm looking for an implementation specialist who
can help with fixing some connection issues and help install a clustered
'Prod ready' install, with the correct config. Installing in Amazon ECS
Containers preferred.
Is there a list somewhere of approved partners/implementors who we can
create an opportunity together?
Thanks,
Iain
6 years, 1 month
