As testing has gotten more robust and expanded (most recently seen in kerberos work by HadoopMarc on TINKERPOP-1641) the need for a module that centralizes some testing functionality has been necessary. We've leaned on gremlin-test for that but that's not really what gremlin-test is for. That module is really for providers to validate aspects of their implementations.
I was thinking that going forward in 3.5.0 we might make some changes where: 1 gremlin-test becomes a simple internal test dependency with some core testing functionality that we need to share across modules 2. we add a new gremlin-test-kit module to be the dependency for provider implementations and extract such functionality from gremlin-test as is necessary. I suppose the other option would be to keep gremlin-test as it is and make some new module called gremlin-test-core (or the like) to hold the common functionality, but that's less nice sounding to me. Any thoughts on the matter?
