E2E testing backend (NESTJS)
# support-questions-legacyj
joemckrusty
03/17/2023, 9:08 AMHi everyone,
I'm currently trying to figure out a way to either mock or integrate supertoken into my backend e2e tests. I would like to have roles and permissions mechanics taken into account whenever I test an endpoint.
Any ideas or even implementation examples on a repo ?
thanks in advance
r
rp_st
03/17/2023, 9:11 AMhey. In your tests, you can call the login endpoint to create a new session and then take it from there.
In terms of the core, you can spin up a new docker container for each test suit with the in memory db and can restart the docker container during each test (to start from a fresh user table for each test), or can create new randomised users during each test.
rp_st
03/17/2023, 9:11 AMthere is no perfect solution to this yet, so it will likely be annoying
rp_st
03/17/2023, 9:11 AMfinally, you can see our github repo's test code for inspiration based on the SDKs that you use
j
joemckrusty
03/17/2023, 7:49 PMI don't want to involve frontend client at all, it's really just testing calls on api endpoints
joemckrusty
03/17/2023, 7:49 PMbooting and restarting a ST instance for EACH test seems like a huge overhead
joemckrusty
03/17/2023, 7:50 PMespecially when the project starts scaling and you have 50 controllers and 10-20 test cases per controller
joemckrusty
03/17/2023, 7:51 PMthat would take an hour or more to launch the e2e test suite alone
joemckrusty
03/17/2023, 7:51 PMwhich is a huge cost in terms of CI time
joemckrusty
03/17/2023, 7:51 PMI'm honestly considering to look for another alternative
joemckrusty
03/17/2023, 7:51 PMbecause that's kind of a deal breaker
joemckrusty
03/17/2023, 7:52 PMI cannot spend months or years working on an API and not being able to test it properly within a reasonable amount of time
joemckrusty
03/17/2023, 7:54 PMI feel like all the development time gained with supertokens initialy, is actually being paid for when you get onto testing
joemckrusty
03/17/2023, 7:58 PMwhich makes me sad, because the project seems very promising
joemckrusty
03/17/2023, 8:00 PMI'll give your testing solution a try and I'll let you know if this is a viable solution
joemckrusty
03/17/2023, 9:23 PM10 seconds average to restart the container....
joemckrusty
03/17/2023, 9:23 PMI'm gonna have to move to keycloak sadly
joemckrusty
03/17/2023, 9:28 PMit would take too much dev time and would be too costly for me to spend time trying to write proper mocks
r
rp_st
03/18/2023, 4:21 AMhey @joemckrusty - you could keep the container started and in each test, create a different user to login. This would remove the restart time for each test entirely.
rp_st
03/18/2023, 4:22 AMIs testing via keycloak any different? It would have the same issue?
6 Views