You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Jonathan Ellithorpe (JIRA)" <ji...@apache.org> on 2015/10/30 00:35:27 UTC
[jira] [Created] (TINKERPOP3-936) Check feature requirements before
opening graph during tests
Jonathan Ellithorpe created TINKERPOP3-936:
----------------------------------------------
Summary: Check feature requirements before opening graph during tests
Key: TINKERPOP3-936
URL: https://issues.apache.org/jira/browse/TINKERPOP3-936
Project: TinkerPop 3
Issue Type: Improvement
Components: test-suite
Affects Versions: 3.0.2-incubating, 3.0.1-incubating, 3.1.0-incubating
Reporter: Jonathan Ellithorpe
Assignee: stephen mallette
Priority: Minor
In AbstractGremlinTest, setup() opens a graph before checking whether or not the graph meets the feature requirements to run the current test. In the case that the graph does not meet the requirements, then opening the graph was wasted work, since the test will not run. For some graph database implementations this wasted work may be trivial, but for others it may be significant (for example, if the graph object must establish connections to remote servers). This wasted work adds up for each test that is skipped.
If there is a way to check the features of a given graph implementation without instantiating a new graph instance, then the order of graph instantiation and feature requirement checking could be reversed, and significantly reduce the time it takes to run a suite of unit tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)