Skip to content

Test script #5

@GoogleCodeExporter

Description

@GoogleCodeExporter
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 lothar.m...@gmail.com on 11 Dec 2012 at 7:35

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions