[jira] [Commented] (TINKERPOP-2443) Improve testing of Translator instances for non-JVM languages with focus on Python as a model

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225404#comment-17225404 ] 

ASF GitHub Bot commented on TINKERPOP-2443:
-------------------------------------------

spmallette merged pull request #1351:
URL: https://github.com/apache/tinkerpop/pull/1351


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Improve testing of Translator instances for non-JVM languages with focus on Python as a model
> ---------------------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2443
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2443
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python, test-suite, translator
>    Affects Versions: 3.4.8
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.5.0
>
>
> It's easy to test a translator like {{GroovyTranslator}} because it runs on the JVM and can hook directly into the standard gremlin-test suite. Off the JVM it's a bit harder because you need a way to run the generated code in the language environment you generated for. So, for {{PythonTranslator}} we would need to hook into the Gherkin tests somehow. I was thinking we could generate a python file on builds that runs through the Gherkin tests to produce the translated version of the Gremlin. That would become a lookup by the test scenario name when executing the Radish tests. In that way we get to test if the translated Gremlin compiles and executes natively. That might also rid ourselves of the "manual" translation we do now in a piece of code like {{feature_steps.py}} which has to string parse Gremlin to produce the compliable Python.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)