question: how to express that ordering doesn't matter?
See original GitHub issueI have a test:
- name: instance list
request:
url: http://localhost:10000/a1-p/policytypes/1006001/policies
method: GET
response:
status_code: 200
body: [qt1, qt2]
how do I express that [qt1, qt2]
OR [qt2,qt1]
is OK? Is there an “unordered_ok” or some equivalent flag?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How To Tell When Order Matters Or Not - Math Stack Exchange
Deciding whether the order matters or not in this case is more of an English problem than a math problem. It's whether the...
Read more >Choosing Things: Does Order Matter? - One Mathematical Cat
Here's another way to think about 'order matters' versus 'order doesn't matter'. Suppose you have three letters (A ...
Read more >What does order matter/doesn't matter actually mean ... - Quora
“Order matters” means that re-arrangements of numbers (— feel free to consider these numbers to be “items” or “events”, if appropriate —) are...
Read more >Combinations (order doesn't matter) and ... - YouTube
Combinations ( order doesn't matter ) and permutations ( order does matter ) ... permutations, chance, tree diagrams … Show more. Show more ......
Read more >Order and Probability | CK-12 Foundation
The order in which you throw in these vegetables doesn't really matter. Here we are talking about a combination. For combinations, you are ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve merged that one and uploaded it to pypi as 1.16.
For a bit of history - this was actually an issue in 2016 when tavern was first being written for an internal use case and it took 5 years to fix!
@michaelboulton Hi! We are currently facing a similar problem. The #604 pull request seems to help solve that. It is now 2021, when will #604 be merged and released and will this issue be resolved?