As a golang ecosystem maintainer I would like to run tests of all golang projects so I can see which tests are passing and which are failing. As build system does not have to provide full environment experience, I want to be able to provide internet access and additional custom configuration.
The emphasis here is to prepare first prototype so I can just run 'gofed-tests test' or similar command. It will install all golang projects and run all tests for each project in a random order. It will report for each tests its status (possible a backtrace) so I can create a statistics and reproduce failed tests. The primary architecture is x86_64. The second step will be to tests only individual tress/graphs of dependencies. So when some golang project is updated, I don't want to run tests of projects, that are not affected by the update.
As a golang ecosystem maintainer I would like to run tests of all golang projects so I can see which tests are passing and which are failing. As build system does not have to provide full environment experience, I want to be able to provide internet access and additional custom configuration.
The emphasis here is to prepare first prototype so I can just run 'gofed-tests test' or similar command. It will install all golang projects and run all tests for each project in a random order. It will report for each tests its status (possible a backtrace) so I can create a statistics and reproduce failed tests. The primary architecture is x86_64. The second step will be to tests only individual tress/graphs of dependencies. So when some golang project is updated, I don't want to run tests of projects, that are not affected by the update.