This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new 40c71b304f Removed some content about the java testing framework.
new 21c784161b Merge branch '3.8-dev'
40c71b304f is described below
commit 40c71b304fbfeb8ad2d0ba8437e6730d414993c7
Author: Stephen Mallette <[email protected]>
AuthorDate: Wed Apr 30 08:25:43 2025 -0400
Removed some content about the java testing framework.
Project has moved on to pure gherkin testing CTR
---
docs/src/dev/developer/for-committers.asciidoc | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/docs/src/dev/developer/for-committers.asciidoc
b/docs/src/dev/developer/for-committers.asciidoc
index 0d203b2848..bc5c2ca72b 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -288,11 +288,8 @@ for an example.
[[gremlin-language-test-cases]]
=== Gremlin Language Test Cases
-Test cases for the Gremlin Language currently requires that the newly
developed test be added in two places:
-
-1. As a test written in Java in the `gremlin-test` module within the
subpackages of
-`org.apache.tinkerpop.gremlin.process.traversal.step`
-2. As a test written in Gherkin in the `gremlin-test` module in the
`/features` subdirectory
+Test cases for the Gremlin Language should be written in Gherkin in the
`gremlin-test` module in the
+`/src/main/resources/org/apache/tinkerpop/gremlin/test/features` subdirectory
When writing a Java test case for a Gremlin step, be sure to use the following
conventions.
@@ -301,13 +298,6 @@ When writing a Java test case for a Gremlin step, be sure
to use the following c
* When creating a test for a step that has both a barrier and sideEffect form
(e.g. `group()`, `groupCount()`, etc.), test both representations.
** `get_g_V_groupCount_byXnameX()`
** `get_g_V_groupCountXaX_byXnameX_capXaX()`
-* The name of the actual test case should be the name of the traversal
generator minus the `get_` prefix.
-* The Gremlin-Groovy version of the test should use the sugar syntax in order
to test sugar (as Gremlin-Java tests test standard syntax).
-** `g.V.age.sum`
-* Avoid using lambdas in the test case unless that is explicitly what is being
tested as OLAP systems will typically not be able to execute those tests.
-* `AbstractGremlinProcessTest` has various static methods to make writing a
test case easy.
-** `checkResults(Arrays.asList("marko","josh"), traversal)`
-** `checkMap(new HashMap<String,Long>() {{ put("marko",1l); }},
traversal.next())`
Gherkin tests follow some important conventions and have a sub-language that
must be adhered to for the tests to
function properly. Note that Gherkin tests are designed to support the testing
of GLVs and at some point will likely
