[
https://issues.apache.org/jira/browse/TINKERPOP3-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495629#comment-14495629
]
Dan LaRocque commented on TINKERPOP3-632:
-----------------------------------------
At the risk of bike shedding this, consider GREMLIN_TESTS. That was my
original suggestion (I never suggested gremlin-tests, which, as Mike noted, is
just as problematic as gremlin.tests when working in a shell).
Although gremlin_tests will probably work everywhere we care about, it defies
the old convention of using only uppercase, digits, and underscores in env var
names. There's long-standing precedent for that on both *NIX and Windows. I
think the convention is also codified somewhere in POSIX.
> Env gremlin.tests should work on all test suites
> ------------------------------------------------
>
> Key: TINKERPOP3-632
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-632
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: test-suite
> Reporter: Matt Frantz
> Priority: Minor
>
> There are some suites that bypass the gremlin.tests env var check in
> ProcessComputerSuite and ProcessStandardSuite by supplying their own list of
> tests. The env var check should be done in AbstractGremlinSuite instead.
> Also, the root README describes using a Maven system property to specify the
> tests, but it has to be an environment variable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
