<p>I'm trying to pick a method of handling properties testing in my Go project. There seems to be 2 options, testing/quick and gopter.</p>
<p>testing/quick is built in to the language which is always a plus, but it seems to be feature dead as it's docs state no new features will be added to it.</p>
<p>gopter on the other hand seems to be under active development, but is an external library and is basically unsearchable as it gets auto-corrected to gopher. </p>
<p>Anyone have any opinions on either of these that can help guide me in making a choice?</p>
<hr/>**评论：**<br/><br/>epiris: <pre><p>I'm not sure what you're asking .. like mentioned already a concrete example would be useful. But since you mentioned testing/quick it's possible what you may want is <a href="https://github.com/dvyukov/go-fuzz" rel="nofollow">fuzzing</a>. Dynamically.. changing a bunch of arbitrary types though whatever that gopter package is doing is likely a false sense of security. The point of testing is to prove the correctness of your program, form strong invariants and prove them methodically. </p>
<p>Fuzzing is something I would use for things that transition to many different states where it's not reasonable or in some cases mathematically viable to cover all possible transitions. It's nice for catching oob/ob1 and lots of other use cases, the repo will cover the topic in depth. Take away here being slinging mud at your functions through code generation has no value add for properly covered code.</p></pre>shovelpost: <pre><blockquote>
<p>I'm trying to pick a method of handling properties testing</p>
</blockquote>
<p>Properties testing? Please give an example and show why you cannot do your testing the standard way.</p></pre>
