Changeset 4978
- Timestamp:
- 1 Feb 2010, 22:11:30 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.sirp/trunk/src/waeup/sirp/doc/developernotes.txt
r4789 r4978 2 2 *************** 3 3 4 How to setup a developer instance of the WAeUP S RP, handle tests, docs4 How to setup a developer instance of the WAeUP SIRP, handle tests, docs 5 5 etc. 6 6 7 The new WAeUP S RP is based on `Grok <http://grok.zope.org/>`_.7 The new WAeUP SIRP 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 S RP we recommend use of17 To create a working copy of the WAeUP SIRP 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 S RP from the subversion server::129 sources of the WAeUP SIRP from the subversion server:: 130 130 131 131 $ cd mysandbox/ 132 $ svn co https://svn.waeup.org/repos/ waeup/tunk waeup-trunk132 $ svn co https://svn.waeup.org/repos/main/waeup.sirp/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 ` package we try to reach high standards in both,197 documentation and testing.198 199 :mod:`waeup ` makes extensive use of doctests, which this way also196 With the :mod:`waeup.sirp` package we try to reach high standards in 197 both, documentation and testing. 198 199 :mod:`waeup.sirp` 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 ` project can easily be created209 doing::208 The documentation of the :mod:`waeup.sirp` project can easily be 209 created doing:: 210 210 211 211 $ bin/waeupdocs 212 212 213 213 This will create a tree of HTML pages in 214 ``parts/waeupdocs/waeup /build/waeup/`` which you can for instance215 browse by pointing your browser to this location.214 ``parts/waeupdocs/waeup.sirp/build/waeup.sirp/`` which you can for 215 instance browse by pointing your browser to this location. 216 216 217 217 An 'official' place in internet for the whole docs is about to come … … 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 ` package226 for examples.225 at the same time. See the many .txt files in the :mod:`waeup.sirp` 226 package for examples. 227 227 228 228 … … 230 230 ======= 231 231 232 Tests are most important to the reliability of the :mod:`waeup `232 Tests are most important to the reliability of the :mod:`waeup.sirp` 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 ` package so that sometimes you249 only want the functional *or* the unit tests to run. This can be done250 like this::248 We have many tests in the :mod:`waeup.sirp` package so that sometimes 249 you only want the functional *or* the unit tests to run. This can be 250 done like this:: 251 251 252 252 $ bin/test -c -u
Note: See TracChangeset for help on using the changeset viewer.