Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

investigate: contract driven, metadata-based property and/or automated testing #43

Open
jimexist opened this issue Nov 27, 2017 · 2 comments
Open

investigate: contract driven, metadata-based property and/or automated testing #43

jimexist opened this issue Nov 27, 2017 · 2 comments
Assignees
@jimexist
Labels
area/test kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone
Long Term

Comments

@jimexist
Copy link
Contributor

jimexist commented Nov 27, 2017 •
edited
Loading

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 ...
@jimexist jimexist self-assigned this Nov 27, 2017
@ddysher ddysher added area/test kind/feature Categorizes issue or PR as related to a new feature. priority/p3 labels Dec 13, 2017
@jimexist jimexist changed the title investigate: contract drive, metadata-based property and/or automated testing investigate: contract driven, metadata-based property and/or automated testing Dec 20, 2017
@kdada kdada mentioned this issue Dec 29, 2017
Closed
24 tasks
@kdada kdada added this to the Long Term milestone Jun 20, 2018
@caicloud-bot
Copy link
Contributor

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

1 similar comment
@caicloud-bot
Copy link
Contributor

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

@caicloud-bot caicloud-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 17, 2018
@bbbmj bbbmj removed the priority/P3 label May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jimexist jimexist

Labels
area/test kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
Long Term
Development

No branches or pull requests
5 participants
@jimexist @ddysher @kdada @caicloud-bot @bbbmj