Implement TypeDBRunner in all clients, extracting the common logic into Kotlin/Bash scripts

[alexjpwalker]

Problem to Solve

Currently each of our 3 clients has a wildly different BDD infrastructure setup:

Client Java

• uses Java class as entry point to each test, linked to Bazel target that passes location of TypeDB Core distro as an argument to the test runner, which TypeDBCoreRunner has access to;
• uses Cucumber's SetUp & TearDown hooks to unzip, run & stop TypeDB via TypeDBCoreRunnerAPI

Client NodeJS

• uses shell script to unzip, run TypeDB, compile client, compile test steps, run tests, and stop TypeDB

Client Python

• uses Bazel rule containing shell commands (copied from client-nodejs) to unzip + run TypeDB, run tests and stop TypeDB

In all clients, the client code and steps are passed in as Bazel dependencies; in client-nodejs, they are both generated on-the-fly using genrules.

Proposed Solution

See Ganesh's message below.

[lolski]

Rather than creating a Bazel rule that starts and stops Grakn at the cost of expressiveness, let's still expose a language specific API for Java, NodeJS, and Python but extract the meat of the logic into Bash / Kotlin, whichever one has less boilerplate and is easy to work with:

• unzipping the archive into unzip.sh
• starting the server into start.sh
• waiting for the port into wait-for-port.sh
• stopping the server into stop.sh
• running command in Console using ./grakn console --script ...: console-script.sh

Supported by these small modules we can implement a very lightweight runner for each language without having to re-implement the logic in each language:

class GraknCoreRunner {
  public void start() {
    ProcessExecutor.execute(unzip.sh);
    ProcessExecutor.execute(start.sh);
    ProcessExecutor.execute(wait-for-port.sh);
  }

  public void consoleScript(String script) {
    ProcessExecutor.execute(console-script.sh, script);
  }
}