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 2015/04/15 14:26:58 UTC

[jira] [Closed] (TINKERPOP3-632) Env gremlin.tests should work on all test suites

     [ https://issues.apache.org/jira/browse/TINKERPOP3-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP3-632.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0.GA
         Assignee: stephen mallette

This was a nice pull request. Thanks.

Sorry [~dalaro] didn't mean to attribute "gremlin-tests" to you - i just flubbed up your recommendation.

> 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
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.0.0.GA
>
>
> 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)