Zend, PHP-Architect and all you others out there praising open source projects… can you please give more priority to really quality work?
I was desperately searching for OXID esales Unit Tests after checking out their community edition from svn. Or are the Unit Tests only accessible for paying customers?
The blog post claiming the 93.x % code coverage:
While searching for it, I came across this forum entry:
http://www.oxid-esales.com/forum/showthread.php?p=12831
Which makes me kind of happy, since I am not the only one who does not just rely on the PHP community back patting the “great” open source projects like WordPress .. and now OXID ?
Curious what the OXID people will reply to this?
I am waiting … also for Zend and PHP Architect on this topic….
August 26, 2009 at 9:10 am |
[...] expect me to be nice … « Trac does not like PHP namespaces either…. oxid esales – show me your 94% Unit Test coverage! [...]
August 26, 2009 at 12:36 pm |
Well, why doesn’t oxid publish its unit tests? The answer is actual pretty simple. We can’t … _yet_ … as our continuous integration and build system does not really allow for it easily at the moment. We develop and maintain only one set of product source code and unit tests for all our shop products… The deployment and building system creates the different editions we have. And we also have 2 commercial editions. The system creates the actual to be released source files with correct license headers and so on. We need to expand the deployment system to also cleanly release the unit tests files. This whole continuous integration and build system of ours was made before we final decided to go open source. To be honest this also makes it a little time consuming for us currently to accept code contributions. As people make their code based on the CE, we need to manually merge that into the larger svn version. True, we still have work here to do here.
We will publish the unit tests sometime in the near feature. However it’s difficult for getting the time to do that. The Product Manager wants to have all the team time
August 26, 2009 at 12:43 pm |
Thanks again Erik.
That is at least an answer.
Suggestion, why dont you just publish the unit tests in the trunk, so people can read them? There are people capable of reading unit tests and making sense out of it
If you cannot or don’t want to publish the unit tests, don’t you think it would be fair to remove statements like 93.x% code coverage and “we have 4000 unit tests”?
so he can put the marketing phrases again!
If you actually remove these marketing statements, believe me, then your Product Manager will give you the time to opensource the unit tests
And as a reminder for us all.. 100% code coverage does not mean at all that your software is bug free.
Still waiting to see the unit tests … maybe you can send me an NDA to sign so I can get access to the unit tests?
Cheers
August 26, 2009 at 9:38 pm |
Nicely done, and thanks for the response. Glad to see someone else noticed my forum post