stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chris snow (JIRA)" <>
Subject [jira] [Resolved] (STRATOS-651) Add a CLI integration test suite
Date Mon, 25 Aug 2014 05:29:57 GMT


chris snow resolved STRATOS-651.

    Resolution: Fixed

> Add a CLI integration test suite
> --------------------------------
>                 Key: STRATOS-651
>                 URL:
>             Project: Stratos
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 4.0.0
>            Reporter: chris snow
>            Assignee: chris snow
>             Fix For: 4.1.0
> I have an integration test suite for the CLI [1].  It currently has about 20 tests, and
has been very useful in testing that fixes on the CLI to give some confidence fixes do not
introduce other defects.
> I originally started writing tests with java and junit.  But jline hangs when testing
the CLI in the same JVM as Junit.  I next looked at using Java ProcessBuilder to execute the
CLI, but that was unreliable and left lots of processes hanging around.  I ended up with the
Python and the pexpect library and wiremock for simulating the REST services.
> I can add some more instructions for adding new tests (e.g. recording REST calls with
wiremock) when this branch gets merged in.
> The changes are contained in the branch: stratos-651-cli-test-suite [1]. In summary:
> - there are some changes to the CLI components pom.xml
> - there is a new src/test/python folder in the CLI component.
> There is a Jenkins build to prove the tests are able to run on maven [2].
> ---
> [1];a=commit;h=cb3a22e8c0a07027e6a90dd6923cce08122a7c15
> [2]

This message was sent by Atlassian JIRA

View raw message