more documentation rST fixes
This commit is contained in:
parent
b55b3a6c67
commit
17dcda30e7
3 changed files with 33 additions and 23 deletions
|
@ -217,6 +217,7 @@
|
|||
<include name="doc/**.rst"/>
|
||||
<include name="doc/**/*.rst"/>
|
||||
<exclude name="doc/LICENSE.txt"/>
|
||||
<exclude name="doc/developers/TODO.rst"/>
|
||||
</fileset>
|
||||
</foreach>
|
||||
</target>
|
||||
|
|
|
@ -4,9 +4,10 @@ How to debug SemanticScuttle
|
|||
|
||||
Database queries
|
||||
----------------
|
||||
In config.php, enable debugMode.
|
||||
Further, add the following there:
|
||||
-------
|
||||
|
||||
In ``data/config.php``, enable ``debugMode``.
|
||||
Further, add the following afterwards: ::
|
||||
|
||||
register_shutdown_function(
|
||||
create_function('', <<<FNC
|
||||
\$GLOBALS['db'] = SemanticScuttle_Service_Factory::getDb();
|
||||
|
@ -14,7 +15,10 @@ register_shutdown_function(
|
|||
FNC
|
||||
)
|
||||
);
|
||||
------
|
||||
To see database queries in SemanticScuttle, add
|
||||
> ?explain=1
|
||||
|
||||
|
||||
To see database queries in SemanticScuttle, add ::
|
||||
|
||||
?explain=1
|
||||
|
||||
to your URL.
|
||||
|
|
|
@ -1,21 +1,26 @@
|
|||
Running unit tests
|
||||
==================
|
||||
|
||||
Go to the SemanticScuttle main directory and run
|
||||
$ php tests/AllTests.php
|
||||
or
|
||||
$ phpunit tests/AllTests.php
|
||||
also remember the --verbose parameter to PHPUnit.
|
||||
Go to the SemanticScuttle ``tests`` directory and run ``phpunit``::
|
||||
|
||||
If you want to run a specific test class only:
|
||||
$ phpunit tests/BookmarksTest.php
|
||||
$ cd tests
|
||||
$ phpunit .
|
||||
|
||||
If you need to test one method only:
|
||||
also remember the ``--verbose`` parameter to PHPUnit.
|
||||
|
||||
If you want to run a specific test class only: ::
|
||||
|
||||
$ cd tests
|
||||
$ phpunit BookmarksTest.php
|
||||
|
||||
If you need to test one method only: ::
|
||||
|
||||
$ cd tests
|
||||
$ phpunit --filter BookmarkTest::testUnificationOfBookmarks tests/BookmarkTest.php
|
||||
|
||||
|
||||
Caveats
|
||||
-------
|
||||
Having debugging enabled and database driver "mysql4" activated
|
||||
will lead to failing tests because of FOUND_ROWS() usage, which
|
||||
Having debugging enabled and database driver "``mysql4``" activated
|
||||
will lead to failing tests because of ``FOUND_ROWS()`` usage, which
|
||||
does not work nicely with database debugging.
|
||||
|
|
Loading…
Reference in a new issue