Thanks stefan.
Wouldn’t just using ExUnit with any HTTP client do the job for you?
That’s what I was thinking (and wondered if other people did the same) but I am not sure how best to integrate that into a phoenix project. My thoughts were to create a special mix command for running them.
On a side note, I would wonder what do you want to achieve, really.
I did think about this. The idea of these tests would be a sort of smoke test. They would test client journeys that contain a sequence of actions a client may carry out against the service, for example:
- sign up
- authenticate
- create a resource
- trigger a workflow
- trigger another workflow
These steps would test high level functionality across many facets of the service in 1 test, only communicating via the REST interface. They test the happy path. I believe I first saw this idea in “Growing Object Orientated Software”.
