Are there any plans to add automated tests to this project?
I think this is crucial, as:
the documentation is sparse (especially for the scriptsdir stuff)
users will download the latest phar (according to the README), breaking existing functionality can be hard to spot (especially as there are no released versions or a CHANGELOG)
First candidates I see would be the scriptsdir stuff (as I also had the most problems with it), to address #34, #56, #57.
In the first step, only package creation can be tested, not deploying itself (which could be added later on). So errors like #35 could be catched.
Are there any plans to add automated tests to this project? I think this is crucial, as:
First candidates I see would be the scriptsdir stuff (as I also had the most problems with it), to address #34, #56, #57.
In the first step, only package creation can be tested, not deploying itself (which could be added later on). So errors like #35 could be catched.
E.g. I could not find documentation on how the "persistent resources" feature is working (which did not in my case): http://files.zend.com/help/Zend-Server/content/understanding_the_package_structure.htm