[
https://issues.apache.org/jira/browse/TINKERPOP-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413973#comment-16413973
]
Roman Kreisel commented on TINKERPOP-1931:
------------------------------------------
Exactly.
This shouldn't be necessary, if both (Client-)API and Server are both tested
against some specification-fulfilling counterpart. But even if both - Client
and Server - work with another specification-conform implementation, they might
not work well together.
If the tests were configureable, it would be possible to (easily) detect such
issues.
> Allow integration tests to be executed against Gremlin Endpoints which don't
> allow anonymous connections
> --------------------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-1931
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1931
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.3.1
> Reporter: Roman Kreisel
> Priority: Major
>
> Right now, it's not possible to run the Gremlin.NET integration tests against
> Gremlin Endpoints, which don't allow connections without user and/or
> password. Some even might only support SSL connections, which also isn't
> supported by most unit tests..
> One of those databases is Microsoft's Cosmos DB.
> Since especially Gremlin.NET might be used often in context of Azure and the
> Cosmos DB, it might be very helpful to have working integration tests against
> this database as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
