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

Test script #5

Open
GoogleCodeExporter opened this issue Oct 23, 2015 · 0 comments
Open

Test script #5

GoogleCodeExporter opened this issue Oct 23, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link
Collaborator

Some automated test tooling is required. However, there are is no unit-test 
framework for shell scripts etc.
I suppose there could be a directory called "tests.d" which contains a bunch of 
shell scripts. Each script there (a test script) is executed by a (to be 
created) test-executor script that will examine the exit code to see if the 
test was successful.

The test executor can also setup any test-fixtures required: environment vars, 
alfresco service start/stop, db and alf_data reset.

The test executor script should be integrated/working when called from jenkins.




Original issue reported on code.google.com by [email protected] on 11 Dec 2012 at 7:35

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

No branches or pull requests

1 participant