Marko A. Rodriguez commented on TINKERPOP-1539:

The problem with creating new graphs in the test is that if the underlying 
graph system doesn't support {{Graph.Features.supportsAddingVertices()}} (e.g. 
Spark/Hadoop/Giraph), then the test would be skipped. So, I  think its okay for 
a couple of tests if need be, but if you can get the desired complexity over 
the Grateful Dead graph, that would be best.

> 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
>            Assignee: Daniel Kuppitz
> 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

Reply via email to