qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cliff Jansen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5307) Change test scripts to cross-platform language
Date Thu, 07 Nov 2013 05:21:17 GMT

    [ https://issues.apache.org/jira/browse/QPID-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815660#comment-13815660
] 

Cliff Jansen commented on QPID-5307:
------------------------------------

My python experience starts and end with qpid/cpp and proton scripting (in CMake and CTest).
 I am not especially knowledgeable about the language compared to shell or powershell usage,
however, I haven't had any issues reading python code or providing fixes as necessary for
Windows.

But I have found, especially in proton work, that 95% or more of the groundwork laid out by
the Linux folk translates directly to Windows.  To be honest, most of the tweaks needed on
Windows have more to do with differences between Visual Studio and make/gmake than they do
with differences between Linux/Unix and Windows.

I am accordingly strongly in favour of python over a duality of separate powershell/batch
scripts and bash/sh scripts.

I can't really speak to whether python is a better alternative than ruby or perl or some other
OS-neutral alternative.

I would note that python is fulfilling this role already in proton (up to 0.5).

Cliff

> Change test scripts to cross-platform language
> ----------------------------------------------
>
>                 Key: QPID-5307
>                 URL: https://issues.apache.org/jira/browse/QPID-5307
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, C++ Client, C++ Clustering
>            Reporter: Steve Huston
>            Assignee: Alan Conway
>              Labels: test
>             Fix For: Future
>
>
> The C++ tree's test suite drivers are primarily shell scripts. Many were duplicated as
Windows PowerShell scripts along the way. However, not all scripts were PowerShell-ized, and
the dual set of test scripts is not maintained in sync. Someone (Cliff?) suggested a while
back that the test driver scripts be written in a common language across Linux and Windows,
and for other platforms as well.
> Python, Perl, Ruby are all possible choices - python and ruby need to be on build systems
anyway for code generation. What do people think about a) this idea in general, b) language
to use?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message