Checking a hash set created with map is failing

[8tomat8]

In one of our applications, we are using HSet to create a Redis hash map. We've been using the map syntax:

cmd, err := redisCli.HSet("key", map[string]interface{}{"1": "one", "2": "two"})

The request is later unpacked into a slice of arguments (which is native for Redis). But as it was passed as a map, the order every time is different. Then in the mock.match function we iterate over the list of expected args and comparing it to the list of cmd args. This function accesses the elements by index, so chances of getting a match decrease with each new item added into the hash :smile:

Workaround: Use the slice syntax instead:

cmd, err := redisCli.HSet("key", []string{"1", "one", "2", "two"})

It is more confusing but works :slightly_smiling_face:

I'm not really sure what could be a good approach to handle this :confused: Possible solutions on my mind:

• Give the option to ignore an order of the argument pairs in tests. The same way as it is done with the mock.MatchExpectationsInOrder(true) option
• Add a check in the match function to ignore an order of the pairs if the called operation supports map syntax

[monkey92t]

sorry, i just saw your problem, i will fix it today.

[8tomat8]

@monkey92t thanks a lot!