[
https://issues.apache.org/jira/browse/TINKERPOP-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette updated TINKERPOP-2601:
----------------------------------------
Description:
We currently use Gherkin for testing GLVs, translators and the grammar. The
final step is to get Gherkin tests acting as the primary tests in the Gremlin
Test Suite itself so that they may be run on the JVM for providers. Initially,
at least in 3.6.0, it makes sense to maintain the old tests where they are but
the ultimate goal should be to deprecate and remove the process suite and make
the structure suite optional. In this way we aren't too opinionated about how
providers implement their graph and are only interested in enforcing Gremlin
semantics
Given improvements in {{null}} handling on TINKERPOP-2605 a lot of new gherkin
tests are arriving. Need to add null annotations for graphs that can store null
and include testing for such cases. This might be a separate issue, but for
tying it to this one for now.
was:We currently use Gherkin for testing GLVs, translators and the grammar.
The final step is to get Gherkin tests acting as the primary tests in the
Gremlin Test Suite itself so that they may be run on the JVM for providers.
Initially, at least in 3.6.0, it makes sense to maintain the old tests where
they are but the ultimate goal should be to deprecate and remove the process
suite and make the structure suite optional. In this way we aren't too
opinionated about how providers implement their graph and are only interested
in enforcing Gremlin semantics
> Unify Gremlin testing behind Gherkin
> ------------------------------------
>
> Key: TINKERPOP-2601
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2601
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.4.12
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
>
> We currently use Gherkin for testing GLVs, translators and the grammar. The
> final step is to get Gherkin tests acting as the primary tests in the Gremlin
> Test Suite itself so that they may be run on the JVM for providers.
> Initially, at least in 3.6.0, it makes sense to maintain the old tests where
> they are but the ultimate goal should be to deprecate and remove the process
> suite and make the structure suite optional. In this way we aren't too
> opinionated about how providers implement their graph and are only interested
> in enforcing Gremlin semantics
> Given improvements in {{null}} handling on TINKERPOP-2605 a lot of new
> gherkin tests are arriving. Need to add null annotations for graphs that can
> store null and include testing for such cases. This might be a separate
> issue, but for tying it to this one for now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
