[
https://issues.apache.org/jira/browse/TINKERPOP-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1517.
---------------------------------------
Resolution: Won't Do
I don't think I want to touch the test suite at this stage. The goal for TP4 is
to build a language agnostic test suite that doesn't rely on the JVM so any
further innovation here doesn't seem to make sense especially since such work
will introduce breaks and risk to something that most providers seem to have
come to grips with in one form of workaround or another. Probably best to just
leave it alone at this stage of things.
> 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
> Priority: Major
> Labels: breaking
>
> 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
(v7.6.3#76005)
