The == operator does not care about order when comparing maps. This applies for structs too.

%{key1: :equal, key2: :values} == %{key2: :values, key1: :equal}
#=> true
%{key1: :unequal, key2: :values} == %{key2: :values, key1: :equal}
#=> false

For tests, you can just assert map1 == map2 as you would expect.

Again, what is wrong with a simple map_a == map_b ?

just adding to that, if you’re talking about tests… if you pattern match you can just look for the stuff you care for in a particular test run… so that works

assert %{field: :i_care_for} = %MyStruct{field: :i_care_for, other_field: :dont_care_about}

can you give me some example of map comparison that is failing? It should not be failing even if the order of fields looks different for some reason.

Absolutely nothing == operator is the best way to do it. For some reason my brain went for a more complex approach