[
https://issues.apache.org/jira/browse/TINKERPOP3-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-906:
----------------------------------------
Fix Version/s: (was: 3.1.0-incubating)
That's a crazy bug. I removed this from 3.1.0-incubating as it seems we are
now dependent on groovy for a fix.
Does this mean that when the bug is fixed that the test order won't matter
anymore (i.e. the tests as-is can execute in any order without problems)?
> Revise DependencyGrabberTest to not be order dependent
> ------------------------------------------------------
>
> Key: TINKERPOP3-906
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-906
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: groovy
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: Jason Plurad
>
> The {{DependencyGrabberTest}} currently require ordered execution based on
> the name of the test. In some environments this seems to cause the tests to
> fail (as they may execute out of order). Generally speaking though it seems
> it would be best if the tests didn't have dependencies on each other in order
> to pass.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
