[TINKERPOP-2622] Enforce ordering semantics in feature tests

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0
• Fix Version/s: 3.7.0, 3.6.2
• Component/s: test-suite
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 15/Sep/21 11:22
• Updated: 11/Jan/23 17:01
• Resolved: 11/Jan/23 17:01

Description

The semantics for ordering aren't always clear and aren't particularly enforced especially when it comes to side-effects. We tend to take the position that Gremlin processes results as they arrive and it is that order that is maintained, but the test suite can be at odds with that as many tests are written without a specific processing order in mind and some implementations may not internally process traversers in the same order. For example consider g_V_group_byXageX which currently fails for Spark as V() returns in a different order there than how the assertion is written:

gremlin> g.V().group().by("age")
==>[null:[v[3],v[5]],32:[v[4]],35:[v[6]],27:[v[2]],29:[v[1]]]
gremlin> g.V().order().by('name').group().by("age")
==>[32:[v[4]],null:[v[3],v[5]],35:[v[6]],27:[v[2]],29:[v[1]]]

We could try to enforce order as shown above but a more flexible assertion system for gherkin seems like a better choice for these cases. As of right now, tests that fail in this fashion are ignored.

Issue Links

• relates to: TINKERPOP-2641 Allow orderability on any type