blob: ae7edade408a8c6c2f98f286fbc8bd0a43f7fcd2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<?xml version="1.0" encoding="utf-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section>
<title>
PythonBrokerTest
</title>
<section role="h2" id="PythonBrokerTest-PythonBrokerSystemTestSuite">
<title>
Python Broker System Test Suite
</title>
<para>
This is a suite of python client tests that exercise and verify
broker functionality. Python allows us to rapidly develop client
test scenarios and provides a 'neutral' set of tests that can run
against any AMQP-compliant broker.
</para>
<para>
The python/tests directory contains a collection of python
modules, each containing several unittest classes, each
containing a set of test methods that represent some test
scenario. Test classes inherit qpid.TestBas from
qpid/testlib.py, it inherits unittest.TestCase
but adds some qpid-specific setUp/tearDown and
convenience functions.
</para>
<para>
TODO: get pydoc generated up to qpid wiki or website
automatically?
</para>
<section role="h3" id="PythonBrokerTest-Runningthetests">
<title>
Running the tests
</title>
<para>
Simplest way to run the tests:
</para>
<itemizedlist>
<listitem>
<para>Run a broker on the default port
</para>
</listitem>
<listitem>
<para>
./run_tests
</para>
</listitem>
</itemizedlist>
<para>
For additional options: ./run_tests --help
</para>
<!--h3-->
</section>
<section role="h3" id="PythonBrokerTest-Expectedfailures">
<title>
Expected failures
</title>
<para>
Until we complete functionality, tests may fail because the
tested functionality is missing in the broker. To skip
expected failures in the C++ or Java brokers:
</para>
<programlisting>
./run_tests -I cpp_failing.txt
./run_tests -I java_failing.txt
</programlisting>
<para>
If you fix a failure, please remove it from the corresponding
list.
</para>
<!--h3-->
</section>
<!--h2-->
</section>
</section>
|
