Property Based Developer Testing - Revision history

Pholser at 15:52, 26 August 2013

2013-08-26T15:52:26Z

← Older revision		Revision as of 08:52, 26 August 2013
Line 2:		Line 2:

	Proposed by [[Paul Holser]]		Proposed by [[Paul Holser]]

			* Amounts to adding "for-all" style assertions about a function to some "there-exists" style tests.
			* Works best on already-TDD'ed code. TDD builds up designs example by example. Hard to see the "for-all" statements without data point to triangulate from.
			* Agitar does something similar -- execute code using lots of different kinds of inputs, possibly deriving interesting data points by inspecting the test subject itself...
			* Works well on already "math-y" domains
			* Drives you, if you're paying attention, away from Primitive Obsession and modeling things like SKUs, Prices, SSNs, etc. as first-class concepts. Otherwise generators miss too much, or try to create invalid things.

	= Literature =		= Literature =

2013-08-24T15:30:25Z

← Older revision		Revision as of 08:30, 24 August 2013
Line 4:		Line 4:

	= Literature =		= Literature =
			* [http://natpryce.com/articles/000802.html Property Based TDD at SPA 2013]
			* [http://shareandenjoy.saff.net/tdd-specifications.pdf The Practice of Theories: Adding "For-all" Statements to "There-exists" tests]
	* [http://debasishg.blogspot.com/2012/07/property-based-testing-for-domain-models.html Property based testing for domain models]		* [http://debasishg.blogspot.com/2012/07/property-based-testing-for-domain-models.html Property based testing for domain models]
	* [http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html Property-based testing: What is it?]		* [http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html Property-based testing: What is it?]
Line 9:		Line 11:
	* [http://www.slideshare.net/FranklinChen/handout-18644963 Beyond xUnit exampled-based testing: property-based testing with ScalaCheck]		* [http://www.slideshare.net/FranklinChen/handout-18644963 Beyond xUnit exampled-based testing: property-based testing with ScalaCheck]
	* [https://gist.github.com/npryce/4147916 Property-Based Testing Tools]		* [https://gist.github.com/npryce/4147916 Property-Based Testing Tools]
			* [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.208.6016&rep=rep1&type=pdf Theory-infected: Or How I Learned to Stop Worrying and Love Universal Quantiﬁcation]

	= Tooling: =		= Tooling: =

2013-08-24T15:25:55Z

@@ Line 2: / Line 2: @@
 Proposed by [[Paul Holser]]
 = Tooling: =
@@ Line 16: / Line 23: @@
 * [https://github.com/DRMacIver/hypothesis Hypothesis]
 * [https://github.com/dbravender/qc qc]

2013-08-24T15:19:08Z

← Older revision		Revision as of 08:19, 24 August 2013
Line 3:		Line 3:
	Proposed by [[Paul Holser]]		Proposed by [[Paul Holser]]

	https://github.com/pholser/junit-quickcheck/		= Tooling: =

			== Java ==
			* [https://github.com/pholser/junit-quickcheck/ junit-quickcheck]
			* [https://bitbucket.org/blob79/quickcheck QuickCheck]
			* [http://www.jcheck.org/ JCheck]

			== Scala ==
			* [https://github.com/rickynils/scalacheck ScalaCheck]

			== Python ==
			* [https://github.com/DRMacIver/hypothesis Hypothesis]
			* [https://github.com/dbravender/qc qc]

2013-08-24T14:52:31Z

← Older revision		Revision as of 07:52, 24 August 2013
Line 1:		Line 1:
	Session at [[CITCONNA2013Sessions]]		Session at [[CITCONNA2013Sessions]]

			Proposed by [[Paul Holser]]

	https://github.com/pholser/junit-quickcheck/		https://github.com/pholser/junit-quickcheck/

2013-08-24T14:42:40Z

Add back link to sessions page

← Older revision		Revision as of 07:42, 24 August 2013
Line 1:		Line 1:
			Session at [[CITCONNA2013Sessions]]

	https://github.com/pholser/junit-quickcheck/		https://github.com/pholser/junit-quickcheck/

2013-08-24T14:41:09Z

Created page with " https://github.com/pholser/junit-quickcheck/"

New page

https://github.com/pholser/junit-quickcheck/