Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated tests #59

Closed
boedah opened this issue Apr 14, 2015 · 2 comments
Closed

Automated tests #59

boedah opened this issue Apr 14, 2015 · 2 comments

Comments

@boedah
Copy link
Contributor

boedah commented Apr 14, 2015

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.

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

slaff pushed a commit that referenced this issue Apr 20, 2015
@slaff
Copy link
Contributor

slaff commented Apr 23, 2015

CI using Travis is now part of the project.( See commits: ecdab08, f56d829 )

@slaff slaff closed this as completed Apr 23, 2015
@boedah
Copy link
Contributor Author

boedah commented Apr 24, 2015

👍 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants