This repository defines the common rules for all test runners:
https://github.com/exercism/automated-tests
There are basically 2 files in there, one defining things about docker, the other how the test runner interface should look like (input, output)
Looking at how other languages like C#, Ruby, JS, etc. have implemented their test runners can also help.
As far as the docker is concerned, the Dockerfile in the go-analyzer repo can be an additional help.
This repository currently only contains a proof of concept on how to convert the output of go test --json in the json output defined in the automated-tests repository above. (interface is probably not yet implemented 100%).
Steps I think need to be done
Building a complete script that runs go test --json and then transforms the output according to the defined interface.
Wrap that script into a docker container according the docker file rules.
This repository defines the common rules for all test runners: https://github.com/exercism/automated-tests There are basically 2 files in there, one defining things about docker, the other how the test runner interface should look like (input, output)
Looking at how other languages like C#, Ruby, JS, etc. have implemented their test runners can also help.
As far as the docker is concerned, the Dockerfile in the go-analyzer repo can be an additional help.
This repository currently only contains a proof of concept on how to convert the output of
go test --jsonin the json output defined in theautomated-testsrepository above. (interface is probably not yet implemented 100%).Steps I think need to be done
go test --jsonand then transforms the output according to the defined interface.Feel free to reorganise, rewrite as you see fit.