Author: phd
Date: 2008-07-23 07:58:11 -0600 (Wed, 23 Jul 2008)
New Revision: 3521
Modified:
SQLObject/trunk/docs/DeveloperGuide.txt
Log:
Minor documentation update - fixed devguide on how to pass DB URI to tests.
Modified: SQLObject/trunk/docs/DeveloperGuide.txt
===================================================================
--- SQLObject/trunk/docs/DeveloperGuide.txt 2008-07-23 13:57:48 UTC (rev 3520)
+++ SQLObject/trunk/docs/DeveloperGuide.txt 2008-07-23 13:58:11 UTC (rev 3521)
@@ -152,11 +152,9 @@
.. _getting started: http://codespeak.net/py/dist/test.html#starting-point-py-test-command-line-tool
To actually run the test, you have to give it a database to connect
-to. You do this with the ``TESTDB`` environmental variable (right now
-py.test doesn't have a better way to add custom options). You can
-give the complete URI to access your test database, or you can give it
-a shortcut like ``mysql`` (these shortcuts are defined in the top of
-``tests/dbtest.py``.
+to. You do so with the option "-D". You can either give a complete URI or one of several
+shortcuts like ``mysql`` (these shortcuts are defined in the top of
+``tests/dbtest.py``).
All the tests are modules in ``sqlobject/tests``. Each module tests
one kind of feature, more or less. If you are testing a module, call

Author: phd
Date: 2008-07-23 07:57:48 -0600 (Wed, 23 Jul 2008)
New Revision: 3520
Modified:
SQLObject/branches/0.10/docs/DeveloperGuide.txt
Log:
Minor documentation update - fixed devguide on how to pass DB URI to tests.
Modified: SQLObject/branches/0.10/docs/DeveloperGuide.txt
===================================================================
--- SQLObject/branches/0.10/docs/DeveloperGuide.txt 2008-07-23 13:57:17 UTC (rev 3519)
+++ SQLObject/branches/0.10/docs/DeveloperGuide.txt 2008-07-23 13:57:48 UTC (rev 3520)
@@ -152,11 +152,9 @@
.. _getting started: http://codespeak.net/py/dist/test.html#starting-point-py-test-command-line-tool
To actually run the test, you have to give it a database to connect
-to. You do this with the ``TESTDB`` environmental variable (right now
-py.test doesn't have a better way to add custom options). You can
-give the complete URI to access your test database, or you can give it
-a shortcut like ``mysql`` (these shortcuts are defined in the top of
-``tests/dbtest.py``.
+to. You do so with the option "-D". You can either give a complete URI or one of several
+shortcuts like ``mysql`` (these shortcuts are defined in the top of
+``tests/dbtest.py``).
All the tests are modules in ``sqlobject/tests``. Each module tests
one kind of feature, more or less. If you are testing a module, call

Author: phd
Date: 2008-07-23 07:57:17 -0600 (Wed, 23 Jul 2008)
New Revision: 3519
Modified:
SQLObject/branches/0.9/docs/DeveloperGuide.txt
Log:
Minor documentation update - fixed devguide on how to pass DB URI to tests.
Modified: SQLObject/branches/0.9/docs/DeveloperGuide.txt
===================================================================
--- SQLObject/branches/0.9/docs/DeveloperGuide.txt 2008-07-19 23:30:05 UTC (rev 3518)
+++ SQLObject/branches/0.9/docs/DeveloperGuide.txt 2008-07-23 13:57:17 UTC (rev 3519)
@@ -152,11 +152,9 @@
.. _getting started: http://codespeak.net/py/dist/test.html#starting-point-py-test-command-line-tool
To actually run the test, you have to give it a database to connect
-to. You do this with the ``TESTDB`` environmental variable (right now
-py.test doesn't have a better way to add custom options). You can
-give the complete URI to access your test database, or you can give it
-a shortcut like ``mysql`` (these shortcuts are defined in the top of
-``tests/dbtest.py``.
+to. You do so with the option "-D". You can either give a complete URI or one of several
+shortcuts like ``mysql`` (these shortcuts are defined in the top of
+``tests/dbtest.py``).
All the tests are modules in ``sqlobject/tests``. Each module tests
one kind of feature, more or less. If you are testing a module, call