diff options
author | Guillermo Ramos | 2020-02-04 13:49:53 +0100 |
---|---|---|
committer | Guillermo Ramos | 2020-02-04 14:20:23 +0100 |
commit | 1566a2fcba0676cf54dde2b04702a320d9f1edcd (patch) | |
tree | 1d6b378f2d5192fbc3f9446ba9a0cd6e8af2c4c7 /test/support/channel_case.ex | |
download | waev-1566a2fcba0676cf54dde2b04702a320d9f1edcd.tar.gz |
Initial commit
Diffstat (limited to 'test/support/channel_case.ex')
-rw-r--r-- | test/support/channel_case.ex | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/test/support/channel_case.ex b/test/support/channel_case.ex new file mode 100644 index 0000000..d1d767f --- /dev/null +++ b/test/support/channel_case.ex @@ -0,0 +1,33 @@ +defmodule WaevWeb.ChannelCase do + @moduledoc """ + This module defines the test case to be used by + channel tests. + + Such tests rely on `Phoenix.ChannelTest` and also + import other functionality to make it easier + to build common data structures and query the data layer. + + Finally, if the test case interacts with the database, + we enable the SQL sandbox, so changes done to the database + are reverted at the end of every test. If you are using + PostgreSQL, you can even run database tests asynchronously + by setting `use WaevWeb.ChannelCase, async: true`, although + this option is not recommended for other databases. + """ + + use ExUnit.CaseTemplate + + using do + quote do + # Import conveniences for testing with channels + use Phoenix.ChannelTest + + # The default endpoint for testing + @endpoint WaevWeb.Endpoint + end + end + + setup _tags do + :ok + end +end |