I'd be interested in learning more about the testing story of PURISTA. Looking at the getting started the only ref is a jest config along with test files. these primarily serve the business logic unit test side of things. In the light of a microservice, event based architecture integration testing becomes much more important though.
So what I'd really like to see is a sample of user and email service, but how one use case like the signup can be properly integration tested in collab
Integration tests are currently not part of the framework itself.
Finding some general approach is difficult - especially because PURISTA is highly modular and stuff like the communication method (MQTT, AMQP...) is not fixed.
You can find a - tbh simple & stupid - example on how to test it, in the repo.
There are some basic integration tests for the event bridges.
so your example is exactly what I was looking for. Creating a fake queue, ramping up a service and performing a command. I'd really add this to your docs as an example for how to run integration testels, even if as you said, the use case is narrowed down to specific constraints. It still gives a good understanding of how to approach it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd be interested in learning more about the testing story of PURISTA. Looking at the getting started the only ref is a jest config along with test files. these primarily serve the business logic unit test side of things. In the light of a microservice, event based architecture integration testing becomes much more important though.
So what I'd really like to see is a sample of user and email service, but how one use case like the signup can be properly integration tested in collab
Integration tests are currently not part of the framework itself.
Finding some general approach is difficult - especially because PURISTA is highly modular and stuff like the communication method (MQTT, AMQP...) is not fixed.
You can find a - tbh simple & stupid - example on how to test it, in the repo.
There are some basic integration tests for the event bridges.
github.com/sebastianwessel/purista...
This will work in mono-repos, but as soon as you have multi-repos, it will not be possible this way.
But, some smart people are working on some interesting stuff:
github.com/traceloop/jest-opentele...
I didn't try it out yet, but on first look, it's promising and might be an option, as PURISTA provides OpenTelemetry out of the box.
so your example is exactly what I was looking for. Creating a fake queue, ramping up a service and performing a command. I'd really add this to your docs as an example for how to run integration testels, even if as you said, the use case is narrowed down to specific constraints. It still gives a good understanding of how to approach it.