[
https://issues.apache.org/jira/browse/TINKERPOP3-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494416#comment-14494416
]
ASF GitHub Bot commented on TINKERPOP3-632:
-------------------------------------------
GitHub user mhfrantz opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/53
TINKERPOP3-632 Enforce gremlin.tests env var in AbstractGremlinSuite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RedSeal-co/incubator-tinkerpop
TINKERPOP3-632-gremlin.tests-env-var
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tinkerpop/pull/53.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #53
----
commit 4e9c94ac3cc5b96117dfc2a7829d5a103e46e88c
Author: mhfrantz <[email protected]>
Date: 2015-04-14T17:11:14Z
TINKERPOP3-632 Enforce gremlin.tests env var in AbstractGremlinSuite
----
> 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)
