The command server running inside the bigtest daemon will be the primary interface for interaction whether through command line interface or through a more complex GUI.
It needs to have both request/response capabilities in order to do things like run a test suite, but it also needs to have realtime capabilities so that interfaces can subscribe to test runs and report results back to the server.
key questions:
What serialization scheme will we use and why?
REST
GRAPHQL
RPC
something else?
What are some key use cases and how will this command flow support them? E.g. launch a browser, run a test suite comprised of multiple tests, and somehow report results back to a command line client.
cowboyd
commented
4 years ago
The command server running inside the bigtest daemon will be the primary interface for interaction whether through command line interface or through a more complex GUI.
It needs to have both request/response capabilities in order to do things like run a test suite, but it also needs to have realtime capabilities so that interfaces can subscribe to test runs and report results back to the server.
key questions:
What serialization scheme will we use and why?
What are some key use cases and how will this command flow support them? E.g. launch a browser, run a test suite comprised of multiple tests, and somehow report results back to a command line client.