atomkirk
Do you think theres a way to write a function that matches a list of patterns with a list of values ignoring order? We use UXID and insert_all in our code a lot (which means all the inserted_at values are the same), which means theres not many options for guaranteeing sort order of results for doing assert […, …] = Repo.all(Model) which means tests are flakey. I just want to test “Records with these shapes were inserted into the db” and I don’t care about order.
@josevalim per https://twitter.com/josevalim/status/1493725996276760582
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Sebb
You could find some inspiration here:
https://github.com/devonestes/assertions/blob/8b353fd941baee8b71181d4e8722c587a5aede87/lib/assertions.ex#L264
just make it take a list of maps to match agains your values.
dimitarvp
They are? That’s surprising. Are you not using microsecond precision of
inserted_atandupdated_at?LostKobrakai
It might sound dump, but if your data has no fixed order, then do not use assertions, which require order.
Enum.findcan do that for example. Testing for the length of lists can also make sure you‘re not missing records or have additional ones.atomkirk
Well with insert_all setting timestamps is up to you cause ecto doesnt do it. So we pass the same value in every record. I don’t know what happens if you generate it at the db level… I guess another solution is to artificially stagger them in code on insert. Thanks for the prompt.
And we do use microsecond precision. Is that enough to GUARANTEE each map created in a loop has uniq timestamp?
dimitarvp
If I were you I’d just not use a hardcoded single value – that’s a meaningless optimization and I can’t believe this would account for anything more than 0.01% performance improvement.
I’d just use
DateTime.utc_now()on each record – but it’s fine to have a single identical value forinserted_atandupdated_at– and then inspect the data myself.IMO dynamically setting up each field as the record gets inserted should be quite enough at the microsecond precision level.
eahanson
You could add a new column just for the purposes of sorting in tests. I’ll sometimes add a sequence column named
seqjust for this.josevalim
Here is a macro (with tests) that matches all elements in the collection matches exactly one pattern in the list:
Better error messages that integrate nicely with ExUnit are left as an exercise to the reader.
atomkirk
Works like a frickin’ charm. This seems generally useful. Do you want me to improve messages (like you said) and offer PR to add to ExUnit.Assertions?
josevalim
At the moment I don’t think it is ExUnit.Assertions material but I will keep an eye open for more use cases!