Commit 437ea7ea authored by Luke Duncalfe's avatar Luke Duncalfe

Fix flaky DesignResolver spec

There is no explicit order currently although one is being introduced in
https://gitlab.com/gitlab-org/gitlab/merge_requests/17788#note_230875678

`contains_exactly` is the correct way to test the resolver, as ordering
isn't important to the resolver itself.

https://gitlab.com/gitlab-org/gitlab/issues/35124
parent 3de90595
...@@ -36,7 +36,7 @@ describe Resolvers::DesignManagement::DesignResolver do ...@@ -36,7 +36,7 @@ describe Resolvers::DesignManagement::DesignResolver do
second_version = create(:design_version) second_version = create(:design_version)
second_design = create(:design, issue: issue, versions: [second_version]) second_design = create(:design, issue: issue, versions: [second_version])
expect(resolve_designs(issue.design_collection, {}, current_user: current_user)).to eq([first_design, second_design]) expect(resolve_designs(issue.design_collection, {}, current_user: current_user)).to contain_exactly(first_design, second_design)
end end
end end
end end
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment