From 28ce31db61a46fbd73126630c758d32a7245da42 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rapha=C3=ABl=20Barrois?= Date: Wed, 6 Jan 2016 23:10:26 +0100 Subject: Clarify the (dis)advantages of randomized tests. As noted in #259, fully random tests have some issues, notably possibly flaky builds: it is quite helpful to be able to choose the random seeds used by factory_boy and friends. --- README.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index 9b82406..8914c62 100644 --- a/README.rst +++ b/README.rst @@ -181,7 +181,7 @@ It is also possible to create a bunch of objects in a single call: Realistic, random values """""""""""""""""""""""" -Tests look better with random yet realistic values. +Demos look better with random yet realistic values; and those realistic values can also help discover bugs. For this, factory_boy relies on the excellent `fake-factory `_ library: .. code-block:: python @@ -199,6 +199,10 @@ For this, factory_boy relies on the excellent `fake-factory +.. note:: Use of fully randomized data in tests is quickly a problem for reproducing broken builds. + To that purpose, factory_boy provides helpers to handle the random seeds it uses. + + Lazy Attributes """"""""""""""" -- cgit v1.2.3