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
99
100
101
102
103
104
105
106
107
108
109
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html>
<head>
<link href="doxygen.css" rel="stylesheet" type="text/css">
<title>Acceptance Tests</title>
</head>
<body>
<div class='header'>
<div class='headertitle'>
Acceptance Tests
</div>
</div>
<div class='contents'>
<p>QuickFIX also has a scriptable test runner that comes with a
series of automated acceptance test. The basic tests that come
with QuickFIX are based off of the <a href=
"http://www.fixprotocol.org/ORGANIZATIONS/928202077/FIX_TestCase_SessionLevel20010710.doc">
FIX Session-level Test Cases and Expected Behaviors</a>
document produced by the FIX protocol organization. These tests
verify that QuickFIX adheres to the FIX specifications. The
automated nature of these tests guarantees that future releases
of QuickFIX will not break any current functionality.</p>
<p>Perhaps even more importantly is how these test are used to
drive the development of QuickFIX. Before a line of code is
written in support of a protocol feature, one of these tests is
written. This test first approach sets up a goal for developers
who will have objective verification that they correctly
implemented the standard.</p>
<p>Below is an example of a test script that tests the engines
behavior when it receives a NewSeqNo value that is less than
the expected MsgSeqNum.</p>
<pre class='fragment'>
iCONNECT
I8=FIX.4.235=A34=149=TW52=>TIME>56=ISLD98=0108=30
E8=FIX.4.29=5735=A34=149=ISLD52=00000000-00:00:0056=TW98=0108=3010=0
# sequence reset without gap fill flag (default to N)
I8=FIX.4.235=434=049=TW52=>TIME>56=ISLD36=1
E8=FIX.4.29=11235=334=249=ISLD52=00000000-00:00:0056=TW45=058=Value is incorrect (out of range) for this tag372=4373=510=0
I8=FIX.4.235=134=249=TW52=>TIME>56=ISLD112=HELLO
E8=FIX.4.29=5535=034=349=ISLD52=00000000-00:00:0056=TW112=HELLO10=0
# sequence reset without gap fill flag (default to N)
I8=FIX.4.235=434=049=TW52=>TIME>56=ISLD36=1123=N
E8=FIX.4.29=11235=334=449=ISLD52=00000000-00:00:0056=TW45=058=Value is incorrect (out of range) for this tag372=4373=510=0
I8=FIX.4.235=134=349=TW52=>TIME>56=ISLD112=HELLO
E8=FIX.4.29=5535=034=549=ISLD52=00000000-00:00:0056=TW112=HELLO10=0
iDISCONNECT
</pre>In these script there are two types of commands, action
commands and messages commands. Action commands begin with
lowercase letters while message command begin with uppercase
letters.
<h2>Action Commands</h2><b>i<ACTION></b> - initiates an
action<br>
<b>e<ACTION></b> - expect (wait for) an action<br>
<br>
Supported actions are:<br>
<br>
<b>iCONNECT</b> - initiate connection to a FIX acceptor<br>
<b>eCONNECT</b> - expect a connection from a FIX initiator<br>
<b>iDISCONNECT</b> - initiate a disconnect<br>
<b>eDISCONNECT</b> - expect a disconnect<br>
<br>
<h2>Message Commands</h2><b>I<MESSAGE></b> - initiate
(send) a message<br>
<b>E<MESSAGE></b> - expect (wait for) a message<br>
<br>
<p>When using the <b>I</b> command, you do not need to add the
<i>Length(9)</i> or the <i>CheckSum(10)</i> fields, they will
be added for you with the correct values in the appropriate
locations. The only time you would add these fields is if you
intentionally wish to make them incorrect.</p>
<p>The <b>I</b> command also provides a TIME macro for fields.
By setting a field equal to <TIME>, the current system
time will be placed in the field. (i.e. 52=>TIME>). You
can also use offsets such as 52=<TIME-120> or
52=<TIME+15> in order to set the time plus or minus some
seconds from the current time.</p>
<p>The <b>E</b> command verifies that you have received the
correct message. This command will compare the values of each
field to make sure they are correct. Some fields cannot be
verified deterministically before run-time such as the
SendingTime and CheckSum fields. These fields can be added to
the <i>fields.fmt</i> file where a regular expression can be
defined to at least verify the field is in the correct format.
For example:</p>10=\d{3}, checksum must be exactly three
digits<br>
52=\d{8}-\d{2}:\d{2}:\d{2}, sending time must be in the form of
DDDDDDDD-DD:DD:DD where D is a digit.
<p>Either command can contain a FILE macro which puts the
contents of a file into a field (i.e.
58=<FILE:test.txt>)</p>
</div>
</body>
</html>
|
