You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "chris snow (JIRA)" <ji...@apache.org> on 2014/05/11 06:54:15 UTC
[jira] [Updated] (STRATOS-651) Add a CLI integration test suite
[ https://issues.apache.org/jira/browse/STRATOS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chris snow updated STRATOS-651:
-------------------------------
Attachment: 0001-fix-for-STRATOS-651.patch
Attached patch for discussion.
> Add a CLI integration test suite
> --------------------------------
>
> Key: STRATOS-651
> URL: https://issues.apache.org/jira/browse/STRATOS-651
> Project: Stratos
> Issue Type: Improvement
> Components: CLI
> Affects Versions: FUTURE
> Reporter: chris snow
> Attachments: 0001-fix-for-STRATOS-651.patch
>
>
> I have an integration test suite for the CLI [1]. It currently has about 18 tests, and has been very useful in testing that fixes on the CLI do not introduce other defects.
> I originally wrote some tests with java and junit, but for the reasons stated in the README.md, I ended up with python.
> I'd like to integrate these tests in to the maven build so the CLI can be automatically tested. I'll need to wrap my python scripts in a maven project, similar to discussed here [2], rather than running the scripts manually from a linux command line.
> ---
> [1] https://github.com/snowch/stratos-cli-test/blob/master/README.md
> [2] http://blog.berczuk.com/2009/12/continuous-integration-of-python-code.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)