[
https://issues.apache.org/jira/browse/TINKERPOP-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1998.
---------------------------------------
Resolution: Done
Assignee: stephen mallette
Fix Version/s: 3.4.1
3.3.6
Added a few additional notes to the dev docs and javadocs. Made some attempt at
making the "schema" more unified but currently I think that's a bit hard to do
at this point and has a higher level of effort than I'd want to invest given
the maturity of the test suite and the core code.
> IoGraphTest use different schemas for standard and readGraph configurations
> ---------------------------------------------------------------------------
>
> Key: TINKERPOP-1998
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1998
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.3.0
> Reporter: Horacio Hoyos Rodriguez
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.3.6, 3.4.1
>
>
> In ArangoDB labels used by vertices and edges must be known in order to
> create a graph. As a result this information should be available at startup,
> i.e via configuration. For example _shouldReadWriteModernToFileWithHelpers_
> test expects a different schema from the *standard* graph than from the
> *readGraph*, the latter attempts to create vertices in a (default) vertex
> collection instead of using the people or software ones that were used for
> the former.
> It would also help, for graph technologies that require schemas, to have a
> document that describe the schemas used/expected in the tests. I am
> collecting this information atm, but having to run failing tests to capture
> what label/edges I am missing for each test is a PITA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
