Changeset 4312 for waeup/branches/ulif-rewrite

Timestamp:

18 Jun 2009, 11:27:25 (15 years ago)

Author:

uli

Message:

Update certificate tests.

File:

• waeup/branches/ulif-rewrite/src/waeup/university/certificate.txt (modified) (4 diffs)

waeup/branches/ulif-rewrite/src/waeup/university/certificate.txt

@@ -6 +6 @@
 Creating certificates
 =====================
+
+Because certificates make use of components registered with the Zope
+Component Architecture (ZCA), we first have to grok the `waeup`
+package. This happens automatically in real-world use:
+
+    >>> import grok
+    >>> grok.testing.grok('waeup')
 
 We can create certificates:
@@ -15 +22 @@
 
 Another way to create certificates is by asking for a factory called
-``waeup.Certificate``. Before we can do this, we have to grok the `waeup`
-package. This happens automatically in real-world use:
-
-    >>> import grok
-    >>> grok.testing.grok('waeup')
-
-Now we can create a factory without importing a class:
+``waeup.Certificate``. This way we can create a factory without
+importing a class:
 
     >>> from zope.component import createObject
@@ -28 +30 @@
     <waeup.university.certificate.Certificate object at 0x...>
 
+
 Certificate attributes
-==================
+======================
 
 Certificates have the attributes required by the `ICertificate` interface:
@@ -59 +62 @@
     >>> mycertificate.code
     u'NA'
+
+`review_state`
+--------------
+
+The review state can have one of the ``checking`` states defined in
+the WAeUP workflow. These are at least the states ``checked`` and
+``unchecked``. After a certificate is created, the review state is
+``unchecked``:
+
+    >>> mycertificate.review_state
+    'unchecked'
+
+We can mark a certificate as checked:
+
+    >>> mycertificate.check()
+    >>> mycertificate.review_state
+    'checked'
+
+We cannot uncheck a certificate:
+
+    >>> mycertificate.review_state = 'init'