[
https://issues.apache.org/jira/browse/QPID-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated QPID-5307:
------------------------------
Comment: was deleted
(was: I"m having trouble with reviewboard so I've attached the patch as
reviews.diff. Sorry for the inconvenience.
I'm a bit behind, I haven't got a new example yet but I've made progress on
getting rid of the test_env.sh/.ps1, and I believe I have an easy route to
allowing tests to be run against a qpid install :)
QPID-5307: brokertest framework: remove dependencies on environment scripts.
The following improvements have been made to the brokertest.py framework,
and the ha_tests.py test module has been updated to take advantage:
- Tests are standard python unittest modules can be run via
qpid-python-test or any python test runner
- Test modules are also executable scripts, they run themselves via
qpid-python-test and accept all arguments that qpid-python-test does.
- No environment settings are required to run the tests, test_env.sh and
test_env.ps1 are not required.
- Configuration formerly in the test_env scripts is provided in
test_config.py
- Only requirement to run tests is that the current directory:
- contains a test_config.py script
- is writable so the tests can create output directories.
- CMake generates a test_config.py suitable for running tests against a
qpid build.
TODO:
- Verify ha_tests.py runs under windows.
- Generate a test_config.py to run tests run against a qpid install.
- Restore windows store configuration removed temporarily.
- Convert some existing .sh/.ps1 script tests to a new test module as
examples.
)
> 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: Steve Huston
> Labels: test
> Fix For: Future
>
> Attachments: review.diff
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
