# Phoenix JSON API acceptance testing

**URL:** <https://forum.elixirforum.com/t/phoenix-json-api-acceptance-testing/16251>\
**Category:** Questions\
**Tags:** phoenix, deployment, testing\
**Created:** [September 2, 2018, 9:43pm UTC](https://forum.elixirforum.com/t/phoenix-json-api-acceptance-testing/16251 "2018-09-02T21:43:51Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jamesmintram](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/jamesmintram/32/11606_2.png) [@jamesmintram](https://forum.elixirforum.com/u/jamesmintram)\
**Post date:** [September 3, 2018, 1:21pm UTC](https://forum.elixirforum.com/t/phoenix-json-api-acceptance-testing/16251/3 "2018-09-03T13:21:54Z")

</div>

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”.

---

_[View the full topic](https://forum.elixirforum.com/t/phoenix-json-api-acceptance-testing/16251)._