Re: ArchGenXML unittest product dependencies
Reinout van Rees <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.archetypes.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 7 Dec 2005, Harald Friessnegger wrote: > in appconfig.py i define the dependencies of my product. normally the > following are enough: > DEPENDENCIES=['LinguaPlone', 'RichDocument', 'MxDateTimeField',] > when i generate my unit tests with AGX too, they can't be run, because of > failing dependencies. > > if i define the dependencies like > DEPENDENCIES=[ 'PloneLanguageTool', > 'kupu' > 'LinguaPlone', > 'RichDocument', > 'MxDateTimeField',] > my tests can be run. > > however, quickinstaller resolves those dependencies (richdocument > installs kupu, linguaplone the plonelanguagetool) when installing my > product. it would be much more convenient if the code that resolves > these dependencies would be generated too. That's a lot of work, I guess. The unittests use the quickinstaller just like plone, the problem is that kupu etc. don't show up in the unittests mock products directory. I'd prefer not really to change anything, but to use PRODUCT_DEPENDENCIES in your AppConfig. That are products that are installed just for your unittests, they're not dependencies for the quickinstaller if you install your product for real (like DEPENDENCIES *is*). This might need a bit of documentation. Most of the options are explained just fine in the generated config.py, btw. I'll look into putting that info on plone.org. Reinout -- Reinout van Rees r.van.rees-1kr/[email protected] http://vanrees.org/weblog/ http://zestsoftware.nl/ "Military engineers build missiles. Civil engineers build targets." ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click