Create empty coverage profile from problem code to calculate coverage
correctly. For some wierd reasons it will also account for not tested packages.
This change prevents students from adding new code and testing it,
instead of getting good coverage for initial codebase :)
Currently, packages in coverme without tests created by student
are not checked for coverage, because no there are no test targets
for them at all!
The issue can be fixed by simply creating empty !change files,
but we are engineers, aren't we? :)
Bonus point: it prevents new packages from giving false coverage credit.
For example, mock file generated by gomock will have lots of covered code
almost instantly. However, the task can be hacked by adding new code to
existing packages.
This seems to be fair, especially since coverage target is
defined problem-wise. Practical reason: coverme/app can not
be covered sufficiently without testing Start/initRoutes/run;
out of these, only initRoutes can be tested, and testing it
separately is a wierd solution.
commit 347ba11cfe4a49bff6fc29063b49416d90525e52
Author: Fedor Korotkiy <prime@yandex-team.ru>
Date: Sat Feb 8 22:44:26 2020 +0300
Sandboxed test execution.
commit c5c9557dd59c54971a78d424ec118655f6b2005c
Author: Fedor Korotkiy <prime@yandex-team.ru>
Date: Sat Feb 8 21:13:13 2020 +0300
Fix paths used during testing.
commit 1ba21eb0aad08f543c6a99bfd927721207943abb
Author: Fedor Korotkiy <prime@yandex-team.ru>
Date: Sat Feb 8 20:56:32 2020 +0300
Helper for process sandboxing
commit 54f0aa11156c1d2c998a060b60be7af8666d5da4
Author: Fedor Korotkiy <prime@yandex-team.ru>
Date: Sat Feb 8 20:10:56 2020 +0300
Package list helper.
