[
https://issues.apache.org/jira/browse/TINKERPOP-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188092#comment-17188092
]
Divij Vaidya commented on TINKERPOP-2412:
-----------------------------------------
No. I am talking specifically about having the as() binding with the steps I
mentioned above such as count(), barrier(), path(), valueMap() etc. AND them
being the only steps which contain as() bindings.
Let's say there was a bug in the addition of requirement logic of the order()
step. The example you quoted above will not catch that bug because Labeled.Path
requirement has already been added to the traversal by the V().as("a"). Hence,
even if there is a bug in order() step's requirement addition, the query will
still produce correct result.
We should have a test case for each step where they are the only ones adding
the LP requirement.
Does that make sense?
> Add missing query tests
> -----------------------
>
> Key: TINKERPOP-2412
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2412
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.4.8
> Reporter: Divij Vaidya
> Priority: Minor
>
> In our Gremlin query test suites, we do not have tests that would test the
> following pattern of queries:
> # "....blah().barrier().as('x')....blah().select('x')"
> # "....blah().valueMap().as('x')....blah().select('x')"
> # "....blah().path().as('x')....blah().select('x')"
> # "....blah().count().as('x')....blah().select('x')"
> The category of tests can be clubbed into defining an alias and using the
> value of the alias further ahead in the traversal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
