Open jimexist opened 7 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Relentless automation!
One shall see that given limited time and efforts, programmers tend to skip writing tests, and code quality plummets when a whole team joins such action. Tests should be automated, if possible.
There should be an investigation into how it can be done with limited efforts from application developers.
There's gopter that was inspired by Scalacheck (which was in turn inspired by Quickcheck). Without a strong type system, Golang automated testing can be done via contracts written in the shape of metadata, etc. and extracted and enforced by reflections.
Let's see where it leads us to ...