You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/10/17 18:49:58 UTC
[jira] [Created] (TINKERPOP-1517) Introduce a GraphProviderSource
stephen mallette created TINKERPOP-1517:
-------------------------------------------
Summary: Introduce a GraphProviderSource
Key: TINKERPOP-1517
URL: https://issues.apache.org/jira/browse/TINKERPOP-1517
Project: TinkerPop
Issue Type: Improvement
Components: test-suite
Affects Versions: 3.2.2
Reporter: stephen mallette
Assignee: stephen mallette
Taken right from the mailing list:
{quote}
We currently tied the GraphProvider to a specific configuration of a Graph instance. So every time you want a slight permutation on that configuration, you need to create a new GraphProvider instance. I think that we can simplify that and cut down on the proliferation of those instances and in the same moment offer some added flexibility. I was digging through JUnit docs/code and I think there is a way for us to create a "GraphProviderSource" which would annotate a test (rather than @GraphProviderClass). The GraphProviderSource would produce a list of GraphProvider instances to run each test in a suite with. So, if the GraphProviderSource produced 4 different GraphProvider instances, it would execute each test in the suite 4 times (one for each GraphProvider).
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)