Fix comments and clean up code in phpCR tests
Most of the comments in the phpCR_* tests still have HTML code or are just taken from the Jackrabbit tests ("Accessing jcr:uuid .... caused an ValueFormatException" should be "... phpCRValueFormatException").
In general, the code layout is not completely clean (which we should strive for) and the code smells a bit like too many comments.
If you use comments, please add an extra tab before the "//" sign so they are indented above the code line they comment.
#2 Updated by Karsten Dambekalns almost 12 years ago
Some additions from #83:
- test case class names don't comply with the naming rules: phpCR_SomeTest instead of T3_phpCR_SomeTest
- @package annotations are mostly wrong, referring to phpCRJackrabbit
- some test methods are static
- some methods are not documented / lack doc comments
In general, some tests look more like functional tests than like unit tests - but I might be wrong with that.