co0lsky
Greetings! I am relatively new to property-based testing. I am practicing writing property tests and hoping for a code review if any practitioner has any comments or suggestions on the test.
defmodule Academy.UserPropTest do
alias Academy.UserShim
use Academy.TestCase, async: true
use PropCheck
use PropCheck.StateM
require ExUnitProperties
# Generators
def first_name() do
StreamData.string(:alphanumeric, length: 10..20)
end
def email() do
StreamData.string(:alphanumeric, length: 10)
end
def email(s) do
attrs = Map.get(s, :existing)
StreamData.constant(attrs.email)
end
def uid() do
StreamData.string(:alphanumeric, length: 10)
end
def uid(s) do
attrs = Map.get(s, :existing)
StreamData.constant(attrs.uid)
end
def role() do
StreamData.member_of(["admin", "editor", "tester", "support", "user"])
end
def profile() do
StreamData.nonempty(StreamData.map_of(StreamData.constant("lang"), StreamData.string(:ascii)))
end
def attrs() do
Enum.take(
StreamData.fixed_map(%{
first_name: first_name(),
email: email(),
uid: uid(),
role: role(),
profile: profile()
}),
1
)
end
def attrs(s) do
Enum.take(
StreamData.fixed_map(%{
first_name: first_name(),
email: email(s),
uid: uid(),
role: role(),
profile: profile()
}),
1
)
end
# Helpers
def like_email(map, email) do
Enum.any?(
Map.values(map),
fn attrs -> attrs.email == email end
)
end
property "user stateful operations", [:verbose] do
forall cmds <- commands(__MODULE__) do
{history, state, result} = run_commands(__MODULE__, cmds)
(result == :ok)
|> aggregate(command_names(cmds))
|> when_fail(
IO.puts("""
History: #{inspect(history)}
State: #{inspect(state)}
Result: #{inspect(result)}
""")
)
end
end
# initial model value at system start. Should be deterministic.
def initial_state(), do: %{}
def command(state) do
always_possible = [
{:call, UserShim, :create, attrs()}
]
relies_on_state =
case Map.equal?(state, %{}) do
# no values yet
true ->
[]
# values from which to work
false ->
s = state
[
{:call, UserShim, :create_existing, attrs(s)}
]
end
oneof(always_possible ++ relies_on_state)
end
# Picks whether a command should be valid under the current state.
def precondition(s, {:call, _, :create, [attrs | _]}) do
not like_email(s, attrs.email)
end
# - all calls with known emails
def precondition(s, {:call, _mod, _fun, [attrs | _]}) do
like_email(s, attrs.email)
end
# Given the state *prior* to the call {:call, mod, fun, args},
# determine whether the result (coming from the actual system)
# makes sense.
def postcondition(_state, {_, _mod, :create, _args}, {:ok, _}) do
true
end
def postcondition(_state, {_, _mod, :create_existing, _args}, {:error, _}) do
true
end
# Assuming the postcondition for a call was true, update the model
# accordingly for the test to proceed
def next_state(
state,
_,
{:call, _, :create, [attrs]}
) do
Map.put(state, :existing, attrs)
end
def next_state(state, _res, {:call, _mod, _fun, _args}) do
new_state = state
new_state
end
end
defmodule Academy.UserShim do
def create(attrs) do
Academy.User.create(attrs)
end
def create_existing(attrs) do
Academy.User.create(attrs)
end
end
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Nothing really wrong pokes me in the eye. Do you want to add to this code but are not able to? That second module is a bit strange though, what’s its purpose?
co0lsky
This is my first time writing a property test. I hope to know if the test has some bad practices.
The second module is a Shim. In my case, I would like to test a different scenario, such as create a user who already exists in the system. By using the shim, I have
:createand:create_existingto indicate different scenarios. So, if calling:create_existing, an error is expecting instead of success.