[
https://issues.apache.org/jira/browse/TINKERPOP-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1378:
----------------------------------------
Labels: (was: test)
This one has been around for a while. At this point, I don't think I'm in favor
of too many more changes to the test suite given that general maturity of
things with TP3. I'm not sure how big a problem this is for your these days but
I was wonder if a workaround might be to make individual {{Graph}} instances in
{{test}} scope, that wrapped a {{SqlgGraph}}. They would be dummies and carry
the specific {{OptOut}} annotations needed per implementation. Your
{{GraphProvider}} would remain unchanged. I tried this with TinkerGraph and it
seemed to worked fine.
{code}
@RunWith(ProcessStandardSuite.class)
@GraphProviderClass(provider = TinkerGraphProvider.class, graph =
OtherTinkerGraph.class)
public class TinkerGraphProcessStandardTest {
}
{code}
Didn't notice any side-effects....I'm going to close this one based on this
workaround. I suppose we can re-open if you feel really strongly about seeing
this resolved some other way, but given the lack of activity here I assume
you've kinda moved on from this or have a suitable approach already. I think
we're going have a much more simple testing model in TP4 when that makes its
way into our discussions.
> Provide a config for Optout
> ---------------------------
>
> Key: TINKERPOP-1378
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1378
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.2.2
> Reporter: pieter martin
> Priority: Minor
>
> Currently the {{OptOut}} annotations are specified directly in the main Graph
> implementation.
> This ticket is to think of a way to specify the {{OptOut}}s in a
> configuration file with test scope.
> A further concern is to add an additional parameter to the configuration to
> name the test suite that the {{OptOut}} applies to.
> The reasoning behind this is that an implementation might itself have
> different underlying databases with different behavior. So by example,
> {{SqlgHsqldbProcessStandardTest}} might {{OptOut}} of different tests to
> {{SqlgGraphPostgresProcessStandardTest}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
