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
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
I’ve followed the Phoenix LiveView file upload code here Uploads — Phoenix LiveView v1.0.0-rc.7 and so far everything works just fine wit...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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.