…ity (return instead of exit). Exit approach seemed to be broken in this case, since always a 200 HTTP status code was returned.

…mponent helper classes iff not already available

…controller

- add: TestSuite which contains the TestCases

… bugfix which is needed for UnitTesting)

…tries to re-define the constants -> errors

- add: missing HttpResponseCodes
- add: try catch during questioning the model because of a possible Erfurt_Ac_Exception exception
- del: some exits

…per, Modified ServiceControllerTest to enable direct execution; Needs to be documented

…g, since it was echoed, when test suite is executed

…d test command

- add: sparqlAction-Test with Query "SELECT ?s WHERE { ?s ?p ?o. }" => Result as XML (#1)
- add: sparqlAction-Test with Query "SELECT ?s WHERE { ?s ?p ?o. }" => Result as JSON (#2)
- both Tests #1 and #2 are questioning an empty/not existable/invisible knowledge base and getting no result, right?

- add: OntoWiki_TestSuite to tests/TestSuite.php
- port: OntoWiki/MessageTest.php into new Test-System
- add: MessageTest to OntoWiki_TestSuite

…are pending.

… message if feed loading fails.

… OntoWiki::APPLICATION_NAME constant.

…ion::VERSION.

…strapping of extension manager still fails, since multiple module registration fails.

… there are errors during tests if not.

…niffer

- add: Makefile options to check all files or only commit files with the codesniffer
- add: codesniffer folder with the ontowiki coding standard
- add: two scripts to manipulate the hgrc file (add/remove codesniffer precommit hook)

- chg: adjust Ontowiki standard
- chg: sniff php files to accepted by the Ontowiki standard
- chg: makefile to check only php files

- chg: all other changes are to fulfill the coding standards

- chg: only one place for config variable in the makefile, so no need to edit
> the 'add-hook' script to chance the severity or something like that

Conflicts:
	Makefile

Neccessary for re-instancing an OntoWiki in PHPUnit,
without it you'll get a warning

- Zend 1.x requires PHPUnit 3.5.x, otherwise you will
  get a warning:

  Declaration of Zend_Test_PHPUnit_Constraint_ResponseHeader::evaluate()
  should be compatible with that of PHPUnit_Framework_Constraint::evaluate()

- many classes were removed in the develop branch, so i did the same during
  merging and adapt the tests (remove some):

  - e.g. OntoWiki/Component/Manager.php

- Lots of tests are broken because of
  - missing functions
  - changed function behavior
  - changed function parameters

  i fix some, uncomment some and there still some which produces errors

- adapt whole test environment and "make test"

  No TestSuites, only TestCases

- An exit stops PHPUnit

- make test-extensions: to test all extensions which have test cases
is still incomplete/broken! Many errors, warnings, ...

…est cases

It is still temporary and should be replace by
clear version as soon as possible!

Conflicts:
	application/controllers/ResourceController.php

Conflicts:
	extensions/queries/lib/SPARQLExecuter.php

….php

…on to prevent PHPUnit from throwing an error

And moving CodeSniffer related stuff to help-cs section

…ing warngins

Conflicts:
	application/tests/OntoWiki/InstancesTest.php
	extensions/history/HistoryController.php
	extensions/queries/QueriesController.php

Add a test case for the class

…wiki_navigation

Conflicts:
	application/classes/OntoWiki/Model/Instances.php
	application/classes/OntoWiki/Model/TitleHelper.php
	application/tests/OntoWiki/Model/InstancesTest.php

And reactivate most of the 56 old tests.

- add response codes for sparql Action
- fix undefined $logout warning
- in ServiceControllerTest the username/password to u/p
- comment out ServiceControllerTest->testAuthActionInvalidUser