From: Demian K. <dem...@vi...> - 2012-07-25 12:34:55
|
> Re modifying the namespace: In other projects I put the test classes in the > same namespace as the class to be tested. Not sure where I picked this up > (supposedly from Symfony2 or Phix) and this wouldn't address the question of > the namespace for TestCase. Using the same namespace as the class to be tested does make sense since it reduces the number of "use" statements required. If you want to change to this approach, I wouldn't object. At the same time, I just noticed that Zend Framework's own test cases use the "ZendTest" top-level namespace... which, as I said before, I don't really like since it seems to violate the principle of using the project / company name as the top-level namespace. We might consider using VuFindTest to be consistent with Zend Framework's approach, but I'd still be happier with either the current approach or the one you just mentioned. > I'll move TestCase, M-x untabify, implement methods for calling static methods > and r/w access to static and non-static properties, recreate the branch and > send a new pull request. Excellent, I'll keep an eye out! - Demian |