Changeset 7823 for main/waeup.custom/trunk/docs/source/developerdocs
- Timestamp:
- 9 Mar 2012, 07:27:06 (13 years ago)
- Location:
- main/waeup.custom/trunk/docs/source/developerdocs
- Files:
-
- 1 deleted
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.custom/trunk/docs/source/developerdocs/developernotes.rst
r6489 r7823 2 2 *************** 3 3 4 How to setup a developer instance of the WAeUP SIRP, handle tests, docs4 How to setup a developer instance of the WAeUP Kofa, handle tests, docs 5 5 etc. 6 6 7 The new WAeUP SIRPis based on `Grok <http://grok.zope.org/>`_.7 The new WAeUP Kofa is based on `Grok <http://grok.zope.org/>`_. 8 8 9 9 Installing a developer copy … … 15 15 -------------------- 16 16 17 To create a working copy of the WAeUP SIRPwe recommend use of17 To create a working copy of the WAeUP Kofa we recommend use of 18 18 `virtualenv`. You, however, need also some basic libraries, a C 19 19 compiler and some things more. … … 127 127 In the sandbox (or anywhere else) we now create our real working 128 128 environment. To do this, we change to the sandbox and checkout the 129 sources of the WAeUP SIRPfrom the subversion server::129 sources of the WAeUP Kofa from the subversion server:: 130 130 131 131 $ cd mysandbox/ 132 $ svn co https://svn.waeup.org/repos/main/waeup. sirp/trunk waeup-trunk132 $ svn co https://svn.waeup.org/repos/main/waeup.kofa/trunk waeup-trunk 133 133 134 134 where ``waeup-trunk`` is only a name we've chosen here to make clear … … 194 194 ============= 195 195 196 With the :mod:`waeup. sirp` package we try to reach high standards in196 With the :mod:`waeup.kofa` package we try to reach high standards in 197 197 both, documentation and testing. 198 198 199 :mod:`waeup. sirp` makes extensive use of doctests, which this way also199 :mod:`waeup.kofa` makes extensive use of doctests, which this way also 200 200 become both: executable (i.e. testable) examples and documentation. 201 201 … … 206 206 documentation generator to generate the docs as HTML pages. 207 207 208 The documentation of the :mod:`waeup. sirp` project can easily be208 The documentation of the :mod:`waeup.kofa` project can easily be 209 209 created doing:: 210 210 … … 212 212 213 213 This will create a tree of HTML pages in 214 ``parts/waeupdocs/waeup. sirp/build/waeup.sirp/`` which you can for214 ``parts/waeupdocs/waeup.kofa/build/waeup.kofa/`` which you can for 215 215 instance browse by pointing your browser to this location. 216 216 … … 223 223 224 224 means explaining to other developers what your code does and test it 225 at the same time. See the many .txt files in the :mod:`waeup. sirp`225 at the same time. See the many .txt files in the :mod:`waeup.kofa` 226 226 package for examples. 227 227 … … 230 230 ======= 231 231 232 Tests are most important to the reliability of the :mod:`waeup. sirp`232 Tests are most important to the reliability of the :mod:`waeup.kofa` 233 233 package. We don't tell someone that our code works, if we cannot prove 234 234 it. And we prove it by testing. … … 246 246 $ bin/test -c 247 247 248 We have many tests in the :mod:`waeup. sirp` package so that sometimes248 We have many tests in the :mod:`waeup.kofa` package so that sometimes 249 249 you only want the functional *or* the unit tests to run. This can be 250 250 done like this:: … … 277 277 278 278 Most unit tests furthermore declare that they want to be run inside 279 the `WAeUP SIRPUnitTestLayer` defined in `waeup.sirp.testing`. This280 layer groks the whole `waeup. sirp` package, so that all ZCA279 the `WAeUPKofaUnitTestLayer` defined in `waeup.kofa.testing`. This 280 layer groks the whole `waeup.kofa` package, so that all ZCA 281 281 components are already setup when you start your tests. 282 282 … … 284 284 layer, the testfile has to provide the following line:: 285 285 286 .. :layer: waeup. sirp.testing.WAeUPSIRPUnitTestLayer286 .. :layer: waeup.kofa.testing.WAeUPKofaUnitTestLayer 287 287 288 288 Use it, if in your tests you make use of registered components like -
main/waeup.custom/trunk/docs/source/developerdocs/index.rst
r6488 r7823 7 7 developernotes 8 8 api/index 9 german/index
Note: See TracChangeset for help on using the changeset viewer.