[
https://issues.apache.org/jira/browse/TINKERPOP-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629163#comment-15629163
]
Daniel Kuppitz commented on TINKERPOP-1539:
-------------------------------------------
Yup, but I don't think we should go too crazy with those tests. Complex queries
in tests should still have a purpose and not just be there, because it's easy
for us to write a 20+ step query. We should prepare the infrastructure for
those tests and then add them on demand. A few good first candidates would be
the queries I'm going to write for
https://issues.apache.org/jira/browse/TINKERPOP-1529.
> Create a ComplexTraversalTest with crazy nested gnarly traversals.
> ------------------------------------------------------------------
>
> Key: TINKERPOP-1539
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1539
> Project: TinkerPop
> Issue Type: Improvement
> Components: process, test-suite
> Affects Versions: 3.2.3
> Reporter: Marko A. Rodriguez
>
> Our {{ProcessSuite}} has numerous tests verifying the semantics of the
> various steps. Unfortunately, these tests are on simple traversals focused on
> exposing the step in question in isolation.
> It would be good to add {{ComplexTraversalTest}} to the {{ProcessSuite}}
> which has traversals over the Grateful Dead graph (for complexity reasons)
> doing:
> 1. Numerous nests.
> 2. Match/Select/Where complexities.
> 3. Global side-effect access and unrolling and injecting.
> 4. ... just a bunch of nasty stuff.
> This will give us much more confidence as we add more strategies and
> potentially, mess up our algebra which isn't exposed by the simple
> "flat'-traversals we current test with.
> [~dkuppitz] --- would you be interested in doing this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
