-
Notifications
You must be signed in to change notification settings - Fork 6
/
Current ConformU Protocol.txt
1400 lines (1389 loc) · 166 KB
/
Current ConformU Protocol.txt
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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
14:04:13.203 Check Alpaca Protocol - Conform Universal 3.1.0 (Build 31181.cb32ac3)
14:04:13.205
14:04:13.205 Test Rotator device: Sample Rotator - 192.168.0.50:5555 through URL: http://192.168.0.50:5555
14:04:13.205
14:04:13.206 Connecting to device...
14:04:13.227 PUT Connected OK ServerTransactionID is correctly cased
14:04:13.228 PUT Connected OK ClientTransactionID is correctly cased
14:04:13.228 PUT Connected OK ErrorNumber is correctly cased
14:04:13.229 PUT Connected OK ErrorMessage is correctly cased
14:04:13.229 PUT Connected OK True - The expected ClientTransactionID was returned: 67890
14:04:13.229 PUT Connected OK True - The ServerTransactionID was 1 or greater: 1205
14:04:13.230 PUT Connected OK True - Received HTTP status 200 (OK) as expected.
14:04:13.230 PUT Connected Response: {"ServerTransactionID": 1205, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.231
14:04:13.231 Successfully connected to device, disconnecting in order to test that connection using a different PUT parameter order is successful...
14:04:13.234 PUT Connected OK ServerTransactionID is correctly cased
14:04:13.234 PUT Connected OK ClientTransactionID is correctly cased
14:04:13.234 PUT Connected OK ErrorNumber is correctly cased
14:04:13.235 PUT Connected OK ErrorMessage is correctly cased
14:04:13.236 PUT Connected OK False - The expected ClientTransactionID was returned: 67890
14:04:13.236 PUT Connected OK False - The ServerTransactionID was 1 or greater: 1206
14:04:13.236 PUT Connected OK False - Received HTTP status 200 (OK) as expected.
14:04:13.236 PUT Connected Response: {"ServerTransactionID": 1206, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.237
14:04:13.237 Successfully disconnected from device, re-connecting using re-ordered PUT parameters...
14:04:13.240 PUT Connected OK ServerTransactionID is correctly cased
14:04:13.240 PUT Connected OK ClientTransactionID is correctly cased
14:04:13.241 PUT Connected OK ErrorNumber is correctly cased
14:04:13.241 PUT Connected OK ErrorMessage is correctly cased
14:04:13.241 PUT Connected OK True - The expected ClientTransactionID was returned: 67890
14:04:13.242 PUT Connected OK True - The ServerTransactionID was 1 or greater: 1207
14:04:13.242 PUT Connected OK True - Received HTTP status 200 (OK) as expected.
14:04:13.242 PUT Connected Response: {"ServerTransactionID": 1207, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.243
14:04:13.250 GET InterfaceVersion OK The expected ClientTransactionID was returned: 67890
14:04:13.250 GET InterfaceVersion OK The ServerTransactionID was 1 or greater: 1208
14:04:13.251 GET InterfaceVersion OK Received HTTP status 200 (OK) as expected.
14:04:13.251 GET InterfaceVersion Response: {"ServerTransactionID": 1208, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.251 Device exposes interface version 4
14:04:13.260 GET Description INFO Bad Alpaca URL base element (api = apx)" - Received HTTP status 404 (NotFound)
14:04:13.261 GET Description Response: {"title": "404 Not Found"}
14:04:13.262 GET Description INFO Bad Alpaca URL version element (no v) - Received HTTP status 404 (NotFound)
14:04:13.263 GET Description Response: {"title": "404 Not Found"}
14:04:13.264 GET Description INFO Bad Alpaca URL version element (no number) - Received HTTP status 404 (NotFound)
14:04:13.265 GET Description Response: {"title": "404 Not Found"}
14:04:13.266 GET Description INFO Bad Alpaca URL version element (capital V) - Received HTTP status 404 (NotFound)
14:04:13.267 GET Description Response: {"title": "404 Not Found"}
14:04:13.268 GET Description INFO Bad Alpaca URL version element (v2) - Received HTTP status 404 (NotFound)
14:04:13.269 GET Description Response: {"title": "404 Not Found"}
14:04:13.270 POST Connected INFO True - Received HTTP status 405 (MethodNotAllowed)
14:04:13.270 POST Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.272 POST Connected INFO Value empty - Received HTTP status 405 (MethodNotAllowed)
14:04:13.273 POST Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.274 POST Connected INFO Number - Received HTTP status 405 (MethodNotAllowed)
14:04:13.274 POST Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.276 DELETE Connected INFO True - Received HTTP status 405 (MethodNotAllowed)
14:04:13.277 DELETE Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.278 DELETE Connected INFO Empty - Received HTTP status 405 (MethodNotAllowed)
14:04:13.279 DELETE Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.280 DELETE Connected INFO Number - Received HTTP status 405 (MethodNotAllowed)
14:04:13.281 DELETE Connected Response: {"title": "405 Method Not Allowed"}
14:04:13.282 GET Description OK Bad Alpaca URL device type (capitalised ROTATOR) - Received HTTP status 404 (NotFound) as expected.
14:04:13.282 GET Description Response: {"title": "404 Not Found"}
14:04:13.284 GET Description OK Bad Alpaca URL device type (baddevicetype) - Received HTTP status 404 (NotFound) as expected.
14:04:13.284 GET Description Response: {"title": "404 Not Found"}
14:04:13.286 GET Description OK Bad Alpaca URL device number (-1) - Received HTTP status 404 (NotFound) as expected.
14:04:13.286 GET Description Response: {"title": "404 Not Found"}
14:04:13.290 GET Description OK Bad Alpaca URL device number (99999) - Received HTTP status 400 (BadRequest) as expected.
14:04:13.290 GET Description Response: {"title": "Bad Alpaca Request", "description": "Device number 99999 does not exist. Maximum device number is 0."}
14:04:13.292 GET Description OK Bad Alpaca URL device number (A) - Received HTTP status 404 (NotFound) as expected.
14:04:13.292 GET Description Response: {"title": "404 Not Found"}
14:04:13.294 GET Description OK Bad Alpaca URL method name (descrip) - Received HTTP status 404 (NotFound) as expected.
14:04:13.294 GET Description Response: {"title": "404 Not Found"}
14:04:13.299 GET Connected OK ServerTransactionID is correctly cased
14:04:13.300 GET Connected OK ClientTransactionID is correctly cased
14:04:13.300 GET Connected OK ErrorNumber is correctly cased
14:04:13.300 GET Connected OK ErrorMessage is correctly cased
14:04:13.301 GET Connected OK JSON Value parameter found OK
14:04:13.301 GET Connected OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.301 GET Connected OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1209
14:04:13.302 GET Connected OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.302 GET Connected Response: {"ServerTransactionID": 1209, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.304 GET Connected OK ServerTransactionID is correctly cased
14:04:13.305 GET Connected OK ClientTransactionID is correctly cased
14:04:13.305 GET Connected OK ErrorNumber is correctly cased
14:04:13.305 GET Connected OK ErrorMessage is correctly cased
14:04:13.306 GET Connected OK JSON Value parameter found OK
14:04:13.306 GET Connected OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.306 GET Connected OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1210
14:04:13.306 GET Connected OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.307 GET Connected Response: {"ServerTransactionID": 1210, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.309 GET Connected OK ServerTransactionID is correctly cased
14:04:13.310 GET Connected OK ClientTransactionID is correctly cased
14:04:13.310 GET Connected OK ErrorNumber is correctly cased
14:04:13.310 GET Connected OK ErrorMessage is correctly cased
14:04:13.310 GET Connected OK JSON Value parameter found OK
14:04:13.311 GET Connected OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.311 GET Connected OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1211
14:04:13.311 GET Connected OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.311 GET Connected Response: {"ServerTransactionID": 1211, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.313 GET Connected OK ServerTransactionID is correctly cased
14:04:13.314 GET Connected OK ClientTransactionID is correctly cased
14:04:13.314 GET Connected OK ErrorNumber is correctly cased
14:04:13.314 GET Connected OK ErrorMessage is correctly cased
14:04:13.314 GET Connected OK JSON Value parameter found OK
14:04:13.315 GET Connected OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.316 GET Connected OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1212
14:04:13.316 GET Connected OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.317 GET Connected Response: {"ServerTransactionID": 1212, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.323 GET Connected OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.324 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.327 GET Connected OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.328 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.330 GET Connected OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.330 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.332 GET Connected OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.333 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.335 GET Connected OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.336 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.338 GET Connected OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.338 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.341 GET Connected OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.341 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.343 GET Connected OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.344 GET Connected Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.346 PUT Connected OK Bad parameter value - Empty string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.346 PUT Connected Response: {"title": "Bad Alpaca Request", "description": "Missing, empty, or misspelled parameter \"Connected\""}
14:04:13.348 PUT Connected OK Bad parameter value - Number - Received HTTP status 400 (BadRequest) as expected.
14:04:13.348 PUT Connected Response: {"title": "Bad Alpaca Request", "description": "Bad boolean value \"123456\""}
14:04:13.350 PUT Connected OK Bad parameter value - Meaningless string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.351 PUT Connected Response: {"title": "Bad Alpaca Request", "description": "Bad boolean value \"asdqwe\""}
14:04:13.353 GET Description OK ServerTransactionID is correctly cased
14:04:13.353 GET Description OK ClientTransactionID is correctly cased
14:04:13.353 GET Description OK ErrorNumber is correctly cased
14:04:13.354 GET Description OK ErrorMessage is correctly cased
14:04:13.354 GET Description OK JSON Value parameter found OK
14:04:13.354 GET Description OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.354 GET Description OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1213
14:04:13.355 GET Description OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.356 GET Description Response: {"ServerTransactionID": 1213, "ClientTransactionID": 67890, "Value": "Sample ASCOM Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.358 GET Description OK ServerTransactionID is correctly cased
14:04:13.358 GET Description OK ClientTransactionID is correctly cased
14:04:13.358 GET Description OK ErrorNumber is correctly cased
14:04:13.359 GET Description OK ErrorMessage is correctly cased
14:04:13.359 GET Description OK JSON Value parameter found OK
14:04:13.359 GET Description OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.359 GET Description OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1214
14:04:13.360 GET Description OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.360 GET Description Response: {"ServerTransactionID": 1214, "ClientTransactionID": 67890, "Value": "Sample ASCOM Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.362 GET Description OK ServerTransactionID is correctly cased
14:04:13.362 GET Description OK ClientTransactionID is correctly cased
14:04:13.362 GET Description OK ErrorNumber is correctly cased
14:04:13.363 GET Description OK ErrorMessage is correctly cased
14:04:13.363 GET Description OK JSON Value parameter found OK
14:04:13.363 GET Description OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.364 GET Description OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1215
14:04:13.364 GET Description OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.364 GET Description Response: {"ServerTransactionID": 1215, "ClientTransactionID": 67890, "Value": "Sample ASCOM Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.366 GET Description OK ServerTransactionID is correctly cased
14:04:13.367 GET Description OK ClientTransactionID is correctly cased
14:04:13.367 GET Description OK ErrorNumber is correctly cased
14:04:13.367 GET Description OK ErrorMessage is correctly cased
14:04:13.367 GET Description OK JSON Value parameter found OK
14:04:13.368 GET Description OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.368 GET Description OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1216
14:04:13.368 GET Description OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.369 GET Description Response: {"ServerTransactionID": 1216, "ClientTransactionID": 67890, "Value": "Sample ASCOM Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.371 GET Description OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.371 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.373 GET Description OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.374 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.377 GET Description OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.377 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.379 GET Description OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.379 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.381 GET Description OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.382 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.384 GET Description OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.384 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.386 GET Description OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.387 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.389 GET Description OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.389 GET Description Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.391 GET DriverInfo OK ServerTransactionID is correctly cased
14:04:13.391 GET DriverInfo OK ClientTransactionID is correctly cased
14:04:13.391 GET DriverInfo OK ErrorNumber is correctly cased
14:04:13.392 GET DriverInfo OK ErrorMessage is correctly cased
14:04:13.392 GET DriverInfo OK JSON Value parameter found OK
14:04:13.392 GET DriverInfo OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.393 GET DriverInfo OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1217
14:04:13.393 GET DriverInfo OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.393 GET DriverInfo Response: {"ServerTransactionID": 1217, "ClientTransactionID": 67890, "Value": "Alpaca Sample Device\nImplements IRotatorV4\nASCOM Initiative", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.396 GET DriverInfo OK ServerTransactionID is correctly cased
14:04:13.396 GET DriverInfo OK ClientTransactionID is correctly cased
14:04:13.397 GET DriverInfo OK ErrorNumber is correctly cased
14:04:13.397 GET DriverInfo OK ErrorMessage is correctly cased
14:04:13.397 GET DriverInfo OK JSON Value parameter found OK
14:04:13.398 GET DriverInfo OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.398 GET DriverInfo OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1218
14:04:13.398 GET DriverInfo OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.399 GET DriverInfo Response: {"ServerTransactionID": 1218, "ClientTransactionID": 67890, "Value": "Alpaca Sample Device\nImplements IRotatorV4\nASCOM Initiative", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.401 GET DriverInfo OK ServerTransactionID is correctly cased
14:04:13.401 GET DriverInfo OK ClientTransactionID is correctly cased
14:04:13.401 GET DriverInfo OK ErrorNumber is correctly cased
14:04:13.401 GET DriverInfo OK ErrorMessage is correctly cased
14:04:13.402 GET DriverInfo OK JSON Value parameter found OK
14:04:13.402 GET DriverInfo OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.402 GET DriverInfo OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1219
14:04:13.402 GET DriverInfo OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.403 GET DriverInfo Response: {"ServerTransactionID": 1219, "ClientTransactionID": 67890, "Value": "Alpaca Sample Device\nImplements IRotatorV4\nASCOM Initiative", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.404 GET DriverInfo OK ServerTransactionID is correctly cased
14:04:13.405 GET DriverInfo OK ClientTransactionID is correctly cased
14:04:13.405 GET DriverInfo OK ErrorNumber is correctly cased
14:04:13.405 GET DriverInfo OK ErrorMessage is correctly cased
14:04:13.405 GET DriverInfo OK JSON Value parameter found OK
14:04:13.406 GET DriverInfo OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.406 GET DriverInfo OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1220
14:04:13.406 GET DriverInfo OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.407 GET DriverInfo Response: {"ServerTransactionID": 1220, "ClientTransactionID": 67890, "Value": "Alpaca Sample Device\nImplements IRotatorV4\nASCOM Initiative", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.408 GET DriverInfo OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.409 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.410 GET DriverInfo OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.411 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.413 GET DriverInfo OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.413 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.416 GET DriverInfo OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.416 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.418 GET DriverInfo OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.419 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.421 GET DriverInfo OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.422 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.423 GET DriverInfo OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.424 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.426 GET DriverInfo OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.426 GET DriverInfo Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.428 GET DriverVersion OK ServerTransactionID is correctly cased
14:04:13.429 GET DriverVersion OK ClientTransactionID is correctly cased
14:04:13.429 GET DriverVersion OK ErrorNumber is correctly cased
14:04:13.429 GET DriverVersion OK ErrorMessage is correctly cased
14:04:13.429 GET DriverVersion OK JSON Value parameter found OK
14:04:13.430 GET DriverVersion OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.430 GET DriverVersion OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1221
14:04:13.431 GET DriverVersion OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.431 GET DriverVersion Response: {"ServerTransactionID": 1221, "ClientTransactionID": 67890, "Value": "0.6", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.433 GET DriverVersion OK ServerTransactionID is correctly cased
14:04:13.433 GET DriverVersion OK ClientTransactionID is correctly cased
14:04:13.433 GET DriverVersion OK ErrorNumber is correctly cased
14:04:13.433 GET DriverVersion OK ErrorMessage is correctly cased
14:04:13.434 GET DriverVersion OK JSON Value parameter found OK
14:04:13.434 GET DriverVersion OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.434 GET DriverVersion OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1222
14:04:13.435 GET DriverVersion OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.435 GET DriverVersion Response: {"ServerTransactionID": 1222, "ClientTransactionID": 67890, "Value": "0.6", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.437 GET DriverVersion OK ServerTransactionID is correctly cased
14:04:13.437 GET DriverVersion OK ClientTransactionID is correctly cased
14:04:13.438 GET DriverVersion OK ErrorNumber is correctly cased
14:04:13.438 GET DriverVersion OK ErrorMessage is correctly cased
14:04:13.438 GET DriverVersion OK JSON Value parameter found OK
14:04:13.438 GET DriverVersion OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.439 GET DriverVersion OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1223
14:04:13.439 GET DriverVersion OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.439 GET DriverVersion Response: {"ServerTransactionID": 1223, "ClientTransactionID": 67890, "Value": "0.6", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.441 GET DriverVersion OK ServerTransactionID is correctly cased
14:04:13.441 GET DriverVersion OK ClientTransactionID is correctly cased
14:04:13.441 GET DriverVersion OK ErrorNumber is correctly cased
14:04:13.442 GET DriverVersion OK ErrorMessage is correctly cased
14:04:13.442 GET DriverVersion OK JSON Value parameter found OK
14:04:13.442 GET DriverVersion OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.442 GET DriverVersion OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1224
14:04:13.443 GET DriverVersion OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.443 GET DriverVersion Response: {"ServerTransactionID": 1224, "ClientTransactionID": 67890, "Value": "0.6", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.445 GET DriverVersion OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.446 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.448 GET DriverVersion OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.448 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.450 GET DriverVersion OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.450 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.452 GET DriverVersion OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.452 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.454 GET DriverVersion OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.455 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.457 GET DriverVersion OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.457 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.459 GET DriverVersion OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.459 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.461 GET DriverVersion OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.462 GET DriverVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.464 GET InterfaceVersion OK ServerTransactionID is correctly cased
14:04:13.464 GET InterfaceVersion OK ClientTransactionID is correctly cased
14:04:13.465 GET InterfaceVersion OK ErrorNumber is correctly cased
14:04:13.465 GET InterfaceVersion OK ErrorMessage is correctly cased
14:04:13.465 GET InterfaceVersion OK JSON Value parameter found OK
14:04:13.465 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.466 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1225
14:04:13.466 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.466 GET InterfaceVersion Response: {"ServerTransactionID": 1225, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.468 GET InterfaceVersion OK ServerTransactionID is correctly cased
14:04:13.469 GET InterfaceVersion OK ClientTransactionID is correctly cased
14:04:13.469 GET InterfaceVersion OK ErrorNumber is correctly cased
14:04:13.469 GET InterfaceVersion OK ErrorMessage is correctly cased
14:04:13.469 GET InterfaceVersion OK JSON Value parameter found OK
14:04:13.470 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.470 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1226
14:04:13.470 GET InterfaceVersion OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.470 GET InterfaceVersion Response: {"ServerTransactionID": 1226, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.472 GET InterfaceVersion OK ServerTransactionID is correctly cased
14:04:13.472 GET InterfaceVersion OK ClientTransactionID is correctly cased
14:04:13.473 GET InterfaceVersion OK ErrorNumber is correctly cased
14:04:13.473 GET InterfaceVersion OK ErrorMessage is correctly cased
14:04:13.473 GET InterfaceVersion OK JSON Value parameter found OK
14:04:13.474 GET InterfaceVersion OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.474 GET InterfaceVersion OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1227
14:04:13.474 GET InterfaceVersion OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.474 GET InterfaceVersion Response: {"ServerTransactionID": 1227, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.477 GET InterfaceVersion OK ServerTransactionID is correctly cased
14:04:13.477 GET InterfaceVersion OK ClientTransactionID is correctly cased
14:04:13.478 GET InterfaceVersion OK ErrorNumber is correctly cased
14:04:13.478 GET InterfaceVersion OK ErrorMessage is correctly cased
14:04:13.478 GET InterfaceVersion OK JSON Value parameter found OK
14:04:13.479 GET InterfaceVersion OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.479 GET InterfaceVersion OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1228
14:04:13.479 GET InterfaceVersion OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.479 GET InterfaceVersion Response: {"ServerTransactionID": 1228, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.481 GET InterfaceVersion OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.482 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.483 GET InterfaceVersion OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.484 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.486 GET InterfaceVersion OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.486 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.488 GET InterfaceVersion OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.488 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.491 GET InterfaceVersion OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.491 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.494 GET InterfaceVersion OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.494 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.496 GET InterfaceVersion OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.496 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.499 GET InterfaceVersion OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.499 GET InterfaceVersion Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.501 GET Name OK ServerTransactionID is correctly cased
14:04:13.501 GET Name OK ClientTransactionID is correctly cased
14:04:13.502 GET Name OK ErrorNumber is correctly cased
14:04:13.502 GET Name OK ErrorMessage is correctly cased
14:04:13.502 GET Name OK JSON Value parameter found OK
14:04:13.502 GET Name OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.503 GET Name OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1229
14:04:13.503 GET Name OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.504 GET Name Response: {"ServerTransactionID": 1229, "ClientTransactionID": 67890, "Value": "Sample Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.506 GET Name OK ServerTransactionID is correctly cased
14:04:13.506 GET Name OK ClientTransactionID is correctly cased
14:04:13.506 GET Name OK ErrorNumber is correctly cased
14:04:13.507 GET Name OK ErrorMessage is correctly cased
14:04:13.508 GET Name OK JSON Value parameter found OK
14:04:13.509 GET Name OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.509 GET Name OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1230
14:04:13.509 GET Name OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.510 GET Name Response: {"ServerTransactionID": 1230, "ClientTransactionID": 67890, "Value": "Sample Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.512 GET Name OK ServerTransactionID is correctly cased
14:04:13.512 GET Name OK ClientTransactionID is correctly cased
14:04:13.512 GET Name OK ErrorNumber is correctly cased
14:04:13.513 GET Name OK ErrorMessage is correctly cased
14:04:13.513 GET Name OK JSON Value parameter found OK
14:04:13.513 GET Name OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.513 GET Name OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1231
14:04:13.514 GET Name OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.514 GET Name Response: {"ServerTransactionID": 1231, "ClientTransactionID": 67890, "Value": "Sample Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.517 GET Name OK ServerTransactionID is correctly cased
14:04:13.517 GET Name OK ClientTransactionID is correctly cased
14:04:13.517 GET Name OK ErrorNumber is correctly cased
14:04:13.517 GET Name OK ErrorMessage is correctly cased
14:04:13.518 GET Name OK JSON Value parameter found OK
14:04:13.518 GET Name OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.518 GET Name OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1232
14:04:13.519 GET Name OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.519 GET Name Response: {"ServerTransactionID": 1232, "ClientTransactionID": 67890, "Value": "Sample Rotator", "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.521 GET Name OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.521 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.524 GET Name OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.524 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.526 GET Name OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.527 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.528 GET Name OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.529 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.531 GET Name OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.532 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.533 GET Name OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.533 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.536 GET Name OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.537 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.539 GET Name OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.539 GET Name Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.541 GET SupportedActions OK ServerTransactionID is correctly cased
14:04:13.541 GET SupportedActions OK ClientTransactionID is correctly cased
14:04:13.541 GET SupportedActions OK ErrorNumber is correctly cased
14:04:13.542 GET SupportedActions OK ErrorMessage is correctly cased
14:04:13.542 GET SupportedActions OK JSON Value parameter found OK
14:04:13.542 GET SupportedActions OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.542 GET SupportedActions OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1233
14:04:13.543 GET SupportedActions OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.543 GET SupportedActions Response: {"ServerTransactionID": 1233, "ClientTransactionID": 67890, "Value": ["MyAction", "YourAction"], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.545 GET SupportedActions OK ServerTransactionID is correctly cased
14:04:13.546 GET SupportedActions OK ClientTransactionID is correctly cased
14:04:13.546 GET SupportedActions OK ErrorNumber is correctly cased
14:04:13.546 GET SupportedActions OK ErrorMessage is correctly cased
14:04:13.546 GET SupportedActions OK JSON Value parameter found OK
14:04:13.547 GET SupportedActions OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.547 GET SupportedActions OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1234
14:04:13.547 GET SupportedActions OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.547 GET SupportedActions Response: {"ServerTransactionID": 1234, "ClientTransactionID": 67890, "Value": ["MyAction", "YourAction"], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.549 GET SupportedActions OK ServerTransactionID is correctly cased
14:04:13.549 GET SupportedActions OK ClientTransactionID is correctly cased
14:04:13.550 GET SupportedActions OK ErrorNumber is correctly cased
14:04:13.550 GET SupportedActions OK ErrorMessage is correctly cased
14:04:13.550 GET SupportedActions OK JSON Value parameter found OK
14:04:13.550 GET SupportedActions OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.551 GET SupportedActions OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1235
14:04:13.551 GET SupportedActions OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.551 GET SupportedActions Response: {"ServerTransactionID": 1235, "ClientTransactionID": 67890, "Value": ["MyAction", "YourAction"], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.553 GET SupportedActions OK ServerTransactionID is correctly cased
14:04:13.554 GET SupportedActions OK ClientTransactionID is correctly cased
14:04:13.554 GET SupportedActions OK ErrorNumber is correctly cased
14:04:13.554 GET SupportedActions OK ErrorMessage is correctly cased
14:04:13.555 GET SupportedActions OK JSON Value parameter found OK
14:04:13.556 GET SupportedActions OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.556 GET SupportedActions OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1236
14:04:13.556 GET SupportedActions OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.557 GET SupportedActions Response: {"ServerTransactionID": 1236, "ClientTransactionID": 67890, "Value": ["MyAction", "YourAction"], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.559 GET SupportedActions OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.559 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.561 GET SupportedActions OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.561 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.564 GET SupportedActions OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.564 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.566 GET SupportedActions OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.567 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.569 GET SupportedActions OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.569 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.571 GET SupportedActions OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.571 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.573 GET SupportedActions OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.574 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.576 GET SupportedActions OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.577 GET SupportedActions Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.579 GET InterfaceVersion OK The expected ClientTransactionID was returned: 67890
14:04:13.579 GET InterfaceVersion OK The ServerTransactionID was 1 or greater: 1237
14:04:13.579 GET InterfaceVersion OK Received HTTP status 200 (OK) as expected.
14:04:13.580 GET InterfaceVersion Response: {"ServerTransactionID": 1237, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.582 GET DeviceState OK ServerTransactionID is correctly cased
14:04:13.582 GET DeviceState OK ClientTransactionID is correctly cased
14:04:13.582 GET DeviceState OK ErrorNumber is correctly cased
14:04:13.583 GET DeviceState OK ErrorMessage is correctly cased
14:04:13.583 GET DeviceState OK JSON Value parameter found OK
14:04:13.583 GET DeviceState OK IsMoving - JSON Name parameter found OK
14:04:13.584 GET DeviceState OK IsMoving - JSON Value parameter found OK
14:04:13.584 GET DeviceState OK MechanicalPosition - JSON Name parameter found OK
14:04:13.585 GET DeviceState OK MechanicalPosition - JSON Value parameter found OK
14:04:13.585 GET DeviceState OK Position - JSON Name parameter found OK
14:04:13.585 GET DeviceState OK Position - JSON Value parameter found OK
14:04:13.585 GET DeviceState OK TimeStamp - JSON Name parameter found OK
14:04:13.585 GET DeviceState OK TimeStamp - JSON Value parameter found OK
14:04:13.586 GET DeviceState OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.586 GET DeviceState OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1238
14:04:13.586 GET DeviceState OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.587 GET DeviceState Response: {"ServerTransactionID": 1238, "ClientTransactionID": 67890, "Value": [{"Name": "IsMoving", "Value": false}, {"Name": "MechanicalPosition", "Value": 0.0}, {"Name": "Position", "Value": 0.0}, {"Name": "TimeStamp", "Value": "2024-09-14T21:04:13.580912"}], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.588 GET DeviceState OK ServerTransactionID is correctly cased
14:04:13.589 GET DeviceState OK ClientTransactionID is correctly cased
14:04:13.589 GET DeviceState OK ErrorNumber is correctly cased
14:04:13.589 GET DeviceState OK ErrorMessage is correctly cased
14:04:13.590 GET DeviceState OK JSON Value parameter found OK
14:04:13.590 GET DeviceState OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:13.590 GET DeviceState OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1239
14:04:13.590 GET DeviceState OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:13.591 GET DeviceState Response: {"ServerTransactionID": 1239, "ClientTransactionID": 67890, "Value": [{"Name": "IsMoving", "Value": false}, {"Name": "MechanicalPosition", "Value": 0.0}, {"Name": "Position", "Value": 0.0}, {"Name": "TimeStamp", "Value": "2024-09-14T21:04:13.587893"}], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.593 GET DeviceState OK ServerTransactionID is correctly cased
14:04:13.593 GET DeviceState OK ClientTransactionID is correctly cased
14:04:13.593 GET DeviceState OK ErrorNumber is correctly cased
14:04:13.594 GET DeviceState OK ErrorMessage is correctly cased
14:04:13.594 GET DeviceState OK JSON Value parameter found OK
14:04:13.594 GET DeviceState OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.594 GET DeviceState OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1240
14:04:13.594 GET DeviceState OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.596 GET DeviceState Response: {"ServerTransactionID": 1240, "ClientTransactionID": 67890, "Value": [{"Name": "IsMoving", "Value": false}, {"Name": "MechanicalPosition", "Value": 0.0}, {"Name": "Position", "Value": 0.0}, {"Name": "TimeStamp", "Value": "2024-09-14T21:04:13.591883"}], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.598 GET DeviceState OK ServerTransactionID is correctly cased
14:04:13.598 GET DeviceState OK ClientTransactionID is correctly cased
14:04:13.599 GET DeviceState OK ErrorNumber is correctly cased
14:04:13.599 GET DeviceState OK ErrorMessage is correctly cased
14:04:13.599 GET DeviceState OK JSON Value parameter found OK
14:04:13.599 GET DeviceState OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:13.600 GET DeviceState OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1241
14:04:13.600 GET DeviceState OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.601 GET DeviceState Response: {"ServerTransactionID": 1241, "ClientTransactionID": 67890, "Value": [{"Name": "IsMoving", "Value": false}, {"Name": "MechanicalPosition", "Value": 0.0}, {"Name": "Position", "Value": 0.0}, {"Name": "TimeStamp", "Value": "2024-09-14T21:04:13.596869"}], "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.603 GET DeviceState OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.603 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.605 GET DeviceState OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.605 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.607 GET DeviceState OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.607 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.609 GET DeviceState OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.610 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.611 GET DeviceState OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.612 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.614 GET DeviceState OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.614 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.617 GET DeviceState OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.617 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.620 GET DeviceState OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.620 GET DeviceState Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.628 GET InterfaceVersion OK The expected ClientTransactionID was returned: 67890
14:04:13.629 GET InterfaceVersion OK The ServerTransactionID was 1 or greater: 1243
14:04:13.629 GET InterfaceVersion OK Received HTTP status 200 (OK) as expected.
14:04:13.629 GET InterfaceVersion Response: {"ServerTransactionID": 1243, "ClientTransactionID": 67890, "Value": 4, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.632 PUT Disconnect OK ServerTransactionID is correctly cased
14:04:13.633 PUT Disconnect OK ClientTransactionID is correctly cased
14:04:13.633 PUT Disconnect OK ErrorNumber is correctly cased
14:04:13.633 PUT Disconnect OK ErrorMessage is correctly cased
14:04:13.634 PUT Disconnect OK Good ID name casing - The expected ClientTransactionID was returned: 67890
14:04:13.634 PUT Disconnect OK Good ID name casing - The ServerTransactionID was 1 or greater: 1244
14:04:13.634 PUT Disconnect OK Good ID name casing - Received HTTP status 200 (OK) as expected.
14:04:13.634 PUT Disconnect Response: {"ServerTransactionID": 1244, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.638 PUT Disconnect OK ServerTransactionID is correctly cased
14:04:13.640 PUT Disconnect OK ClientTransactionID is correctly cased
14:04:13.641 PUT Disconnect OK ErrorNumber is correctly cased
14:04:13.641 PUT Disconnect OK ErrorMessage is correctly cased
14:04:13.645 PUT Disconnect OK Good ID casing + extra parameter - The expected ClientTransactionID was returned: 67890
14:04:13.645 PUT Disconnect OK Good ID casing + extra parameter - The ServerTransactionID was 1 or greater: 1245
14:04:13.645 PUT Disconnect OK Good ID casing + extra parameter - Received HTTP status 200 (OK) as expected.
14:04:13.646 PUT Disconnect Response: {"ServerTransactionID": 1245, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.664 PUT Disconnect OK ServerTransactionID is correctly cased
14:04:13.664 PUT Disconnect OK ClientTransactionID is correctly cased
14:04:13.664 PUT Disconnect OK ErrorNumber is correctly cased
14:04:13.665 PUT Disconnect OK ErrorMessage is correctly cased
14:04:13.665 PUT Disconnect OK Bad ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.665 PUT Disconnect OK Bad ClientID casing - The ServerTransactionID was 1 or greater: 1246
14:04:13.665 PUT Disconnect OK Bad ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.666 PUT Disconnect Response: {"ServerTransactionID": 1246, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.668 PUT Disconnect OK ServerTransactionID is correctly cased
14:04:13.668 PUT Disconnect OK ClientTransactionID is correctly cased
14:04:13.669 PUT Disconnect OK ErrorNumber is correctly cased
14:04:13.669 PUT Disconnect OK ErrorMessage is correctly cased
14:04:13.669 PUT Disconnect OK Bad ClientTransactionID casing - The returned ClientTransactionID was 0 as expected.
14:04:13.669 PUT Disconnect OK Bad ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1247
14:04:13.670 PUT Disconnect OK Bad ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.670 PUT Disconnect Response: {"ServerTransactionID": 1247, "ClientTransactionID": 0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.672 PUT Disconnect OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.672 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.675 PUT Disconnect OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.676 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.678 PUT Disconnect OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.678 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.681 PUT Disconnect OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.681 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.683 PUT Disconnect OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.683 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.685 PUT Disconnect OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.685 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.687 PUT Disconnect OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.688 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.690 PUT Disconnect OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.690 PUT Disconnect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:13.699 PUT Connect OK ServerTransactionID is correctly cased
14:04:13.699 PUT Connect OK ClientTransactionID is correctly cased
14:04:13.699 PUT Connect OK ErrorNumber is correctly cased
14:04:13.700 PUT Connect OK ErrorMessage is correctly cased
14:04:13.700 PUT Connect OK Good ID name casing - The expected ClientTransactionID was returned: 67890
14:04:13.700 PUT Connect OK Good ID name casing - The ServerTransactionID was 1 or greater: 1250
14:04:13.700 PUT Connect OK Good ID name casing - Received HTTP status 200 (OK) as expected.
14:04:13.701 PUT Connect Response: {"ServerTransactionID": 1250, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.703 PUT Connect OK ServerTransactionID is correctly cased
14:04:13.703 PUT Connect OK ClientTransactionID is correctly cased
14:04:13.703 PUT Connect OK ErrorNumber is correctly cased
14:04:13.704 PUT Connect OK ErrorMessage is correctly cased
14:04:13.704 PUT Connect OK Good ID casing + extra parameter - The expected ClientTransactionID was returned: 67890
14:04:13.704 PUT Connect OK Good ID casing + extra parameter - The ServerTransactionID was 1 or greater: 1251
14:04:13.704 PUT Connect OK Good ID casing + extra parameter - Received HTTP status 200 (OK) as expected.
14:04:13.705 PUT Connect Response: {"ServerTransactionID": 1251, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.707 PUT Connect OK ServerTransactionID is correctly cased
14:04:13.707 PUT Connect OK ClientTransactionID is correctly cased
14:04:13.707 PUT Connect OK ErrorNumber is correctly cased
14:04:13.708 PUT Connect OK ErrorMessage is correctly cased
14:04:13.708 PUT Connect OK Bad ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:13.708 PUT Connect OK Bad ClientID casing - The ServerTransactionID was 1 or greater: 1252
14:04:13.709 PUT Connect OK Bad ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:13.709 PUT Connect Response: {"ServerTransactionID": 1252, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.711 PUT Connect OK ServerTransactionID is correctly cased
14:04:13.711 PUT Connect OK ClientTransactionID is correctly cased
14:04:13.712 PUT Connect OK ErrorNumber is correctly cased
14:04:13.712 PUT Connect OK ErrorMessage is correctly cased
14:04:13.712 PUT Connect OK Bad ClientTransactionID casing - The returned ClientTransactionID was 0 as expected.
14:04:13.713 PUT Connect OK Bad ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1253
14:04:13.713 PUT Connect OK Bad ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:13.713 PUT Connect Response: {"ServerTransactionID": 1253, "ClientTransactionID": 0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:13.716 PUT Connect OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.716 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.719 PUT Connect OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.719 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:13.722 PUT Connect OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.722 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:13.724 PUT Connect OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:13.724 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:13.726 PUT Connect OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:13.727 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.729 PUT Connect OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:13.729 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:13.731 PUT Connect OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:13.732 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:13.733 PUT Connect OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:13.734 PUT Connect Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:18.751 GET Connecting OK ServerTransactionID is correctly cased
14:04:18.752 GET Connecting OK ClientTransactionID is correctly cased
14:04:18.753 GET Connecting OK ErrorNumber is correctly cased
14:04:18.754 GET Connecting OK ErrorMessage is correctly cased
14:04:18.755 GET Connecting OK JSON Value parameter found OK
14:04:18.758 GET Connecting OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.761 GET Connecting OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1265
14:04:18.763 GET Connecting OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.764 GET Connecting Response: {"ServerTransactionID": 1265, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.769 GET Connecting OK ServerTransactionID is correctly cased
14:04:18.774 GET Connecting OK ClientTransactionID is correctly cased
14:04:18.775 GET Connecting OK ErrorNumber is correctly cased
14:04:18.775 GET Connecting OK ErrorMessage is correctly cased
14:04:18.776 GET Connecting OK JSON Value parameter found OK
14:04:18.777 GET Connecting OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:18.777 GET Connecting OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1266
14:04:18.778 GET Connecting OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:18.778 GET Connecting Response: {"ServerTransactionID": 1266, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.781 GET Connecting OK ServerTransactionID is correctly cased
14:04:18.781 GET Connecting OK ClientTransactionID is correctly cased
14:04:18.782 GET Connecting OK ErrorNumber is correctly cased
14:04:18.782 GET Connecting OK ErrorMessage is correctly cased
14:04:18.783 GET Connecting OK JSON Value parameter found OK
14:04:18.783 GET Connecting OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:18.783 GET Connecting OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1267
14:04:18.784 GET Connecting OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:18.784 GET Connecting Response: {"ServerTransactionID": 1267, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.786 GET Connecting OK ServerTransactionID is correctly cased
14:04:18.786 GET Connecting OK ClientTransactionID is correctly cased
14:04:18.786 GET Connecting OK ErrorNumber is correctly cased
14:04:18.786 GET Connecting OK ErrorMessage is correctly cased
14:04:18.787 GET Connecting OK JSON Value parameter found OK
14:04:18.787 GET Connecting OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.787 GET Connecting OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1268
14:04:18.787 GET Connecting OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.788 GET Connecting Response: {"ServerTransactionID": 1268, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.794 GET Connecting OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.795 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.798 GET Connecting OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.798 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.800 GET Connecting OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.801 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:18.802 GET Connecting OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:18.802 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:18.804 GET Connecting OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.804 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.806 GET Connecting OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.807 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.809 GET Connecting OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.809 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:18.811 GET Connecting OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:18.811 GET Connecting Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:18.813 GET CanReverse OK ServerTransactionID is correctly cased
14:04:18.814 GET CanReverse OK ClientTransactionID is correctly cased
14:04:18.814 GET CanReverse OK ErrorNumber is correctly cased
14:04:18.814 GET CanReverse OK ErrorMessage is correctly cased
14:04:18.814 GET CanReverse OK JSON Value parameter found OK
14:04:18.815 GET CanReverse OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.815 GET CanReverse OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1269
14:04:18.815 GET CanReverse OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.816 GET CanReverse Response: {"ServerTransactionID": 1269, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.818 GET CanReverse OK ServerTransactionID is correctly cased
14:04:18.819 GET CanReverse OK ClientTransactionID is correctly cased
14:04:18.819 GET CanReverse OK ErrorNumber is correctly cased
14:04:18.820 GET CanReverse OK ErrorMessage is correctly cased
14:04:18.821 GET CanReverse OK JSON Value parameter found OK
14:04:18.821 GET CanReverse OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:18.821 GET CanReverse OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1270
14:04:18.822 GET CanReverse OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:18.822 GET CanReverse Response: {"ServerTransactionID": 1270, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.824 GET CanReverse OK ServerTransactionID is correctly cased
14:04:18.824 GET CanReverse OK ClientTransactionID is correctly cased
14:04:18.824 GET CanReverse OK ErrorNumber is correctly cased
14:04:18.825 GET CanReverse OK ErrorMessage is correctly cased
14:04:18.825 GET CanReverse OK JSON Value parameter found OK
14:04:18.825 GET CanReverse OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:18.825 GET CanReverse OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1271
14:04:18.826 GET CanReverse OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:18.826 GET CanReverse Response: {"ServerTransactionID": 1271, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.828 GET CanReverse OK ServerTransactionID is correctly cased
14:04:18.828 GET CanReverse OK ClientTransactionID is correctly cased
14:04:18.828 GET CanReverse OK ErrorNumber is correctly cased
14:04:18.828 GET CanReverse OK ErrorMessage is correctly cased
14:04:18.829 GET CanReverse OK JSON Value parameter found OK
14:04:18.829 GET CanReverse OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.829 GET CanReverse OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1272
14:04:18.830 GET CanReverse OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.830 GET CanReverse Response: {"ServerTransactionID": 1272, "ClientTransactionID": 67890, "Value": true, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.832 GET CanReverse OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.832 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.834 GET CanReverse OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.834 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.837 GET CanReverse OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.837 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:18.839 GET CanReverse OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:18.840 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:18.842 GET CanReverse OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.842 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.844 GET CanReverse OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.844 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.846 GET CanReverse OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.847 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:18.849 GET CanReverse OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:18.849 GET CanReverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:18.851 GET IsMoving OK ServerTransactionID is correctly cased
14:04:18.851 GET IsMoving OK ClientTransactionID is correctly cased
14:04:18.852 GET IsMoving OK ErrorNumber is correctly cased
14:04:18.852 GET IsMoving OK ErrorMessage is correctly cased
14:04:18.853 GET IsMoving OK JSON Value parameter found OK
14:04:18.853 GET IsMoving OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.853 GET IsMoving OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1273
14:04:18.853 GET IsMoving OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.853 GET IsMoving Response: {"ServerTransactionID": 1273, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.855 GET IsMoving OK ServerTransactionID is correctly cased
14:04:18.855 GET IsMoving OK ClientTransactionID is correctly cased
14:04:18.856 GET IsMoving OK ErrorNumber is correctly cased
14:04:18.856 GET IsMoving OK ErrorMessage is correctly cased
14:04:18.857 GET IsMoving OK JSON Value parameter found OK
14:04:18.857 GET IsMoving OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:18.858 GET IsMoving OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1274
14:04:18.858 GET IsMoving OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:18.858 GET IsMoving Response: {"ServerTransactionID": 1274, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.860 GET IsMoving OK ServerTransactionID is correctly cased
14:04:18.861 GET IsMoving OK ClientTransactionID is correctly cased
14:04:18.861 GET IsMoving OK ErrorNumber is correctly cased
14:04:18.861 GET IsMoving OK ErrorMessage is correctly cased
14:04:18.862 GET IsMoving OK JSON Value parameter found OK
14:04:18.862 GET IsMoving OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:18.862 GET IsMoving OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1275
14:04:18.862 GET IsMoving OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:18.862 GET IsMoving Response: {"ServerTransactionID": 1275, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.864 GET IsMoving OK ServerTransactionID is correctly cased
14:04:18.865 GET IsMoving OK ClientTransactionID is correctly cased
14:04:18.865 GET IsMoving OK ErrorNumber is correctly cased
14:04:18.865 GET IsMoving OK ErrorMessage is correctly cased
14:04:18.866 GET IsMoving OK JSON Value parameter found OK
14:04:18.866 GET IsMoving OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.867 GET IsMoving OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1276
14:04:18.867 GET IsMoving OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.867 GET IsMoving Response: {"ServerTransactionID": 1276, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.869 GET IsMoving OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.869 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.872 GET IsMoving OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.872 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.874 GET IsMoving OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.876 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:18.882 GET IsMoving OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:18.896 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:18.899 GET IsMoving OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.900 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.902 GET IsMoving OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.902 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.904 GET IsMoving OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.904 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:18.906 GET IsMoving OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:18.906 GET IsMoving Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:18.908 GET MechanicalPosition OK ServerTransactionID is correctly cased
14:04:18.908 GET MechanicalPosition OK ClientTransactionID is correctly cased
14:04:18.909 GET MechanicalPosition OK ErrorNumber is correctly cased
14:04:18.909 GET MechanicalPosition OK ErrorMessage is correctly cased
14:04:18.909 GET MechanicalPosition OK JSON Value parameter found OK
14:04:18.909 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.910 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1277
14:04:18.910 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.910 GET MechanicalPosition Response: {"ServerTransactionID": 1277, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.912 GET MechanicalPosition OK ServerTransactionID is correctly cased
14:04:18.913 GET MechanicalPosition OK ClientTransactionID is correctly cased
14:04:18.913 GET MechanicalPosition OK ErrorNumber is correctly cased
14:04:18.913 GET MechanicalPosition OK ErrorMessage is correctly cased
14:04:18.913 GET MechanicalPosition OK JSON Value parameter found OK
14:04:18.914 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:18.914 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1278
14:04:18.914 GET MechanicalPosition OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:18.915 GET MechanicalPosition Response: {"ServerTransactionID": 1278, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.918 GET MechanicalPosition OK ServerTransactionID is correctly cased
14:04:18.918 GET MechanicalPosition OK ClientTransactionID is correctly cased
14:04:18.918 GET MechanicalPosition OK ErrorNumber is correctly cased
14:04:18.919 GET MechanicalPosition OK ErrorMessage is correctly cased
14:04:18.919 GET MechanicalPosition OK JSON Value parameter found OK
14:04:18.919 GET MechanicalPosition OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:18.920 GET MechanicalPosition OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1279
14:04:18.920 GET MechanicalPosition OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:18.920 GET MechanicalPosition Response: {"ServerTransactionID": 1279, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.922 GET MechanicalPosition OK ServerTransactionID is correctly cased
14:04:18.923 GET MechanicalPosition OK ClientTransactionID is correctly cased
14:04:18.923 GET MechanicalPosition OK ErrorNumber is correctly cased
14:04:18.923 GET MechanicalPosition OK ErrorMessage is correctly cased
14:04:18.924 GET MechanicalPosition OK JSON Value parameter found OK
14:04:18.924 GET MechanicalPosition OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.924 GET MechanicalPosition OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1280
14:04:18.924 GET MechanicalPosition OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.925 GET MechanicalPosition Response: {"ServerTransactionID": 1280, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.927 GET MechanicalPosition OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.927 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.929 GET MechanicalPosition OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.930 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.933 GET MechanicalPosition OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.935 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:18.938 GET MechanicalPosition OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:18.941 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:18.943 GET MechanicalPosition OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.944 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.948 GET MechanicalPosition OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.949 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:18.951 GET MechanicalPosition OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.952 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:18.955 GET MechanicalPosition OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:18.955 GET MechanicalPosition Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:18.958 GET Position OK ServerTransactionID is correctly cased
14:04:18.959 GET Position OK ClientTransactionID is correctly cased
14:04:18.959 GET Position OK ErrorNumber is correctly cased
14:04:18.960 GET Position OK ErrorMessage is correctly cased
14:04:18.960 GET Position OK JSON Value parameter found OK
14:04:18.960 GET Position OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.961 GET Position OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1281
14:04:18.961 GET Position OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.962 GET Position Response: {"ServerTransactionID": 1281, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.964 GET Position OK ServerTransactionID is correctly cased
14:04:18.965 GET Position OK ClientTransactionID is correctly cased
14:04:18.965 GET Position OK ErrorNumber is correctly cased
14:04:18.965 GET Position OK ErrorMessage is correctly cased
14:04:18.965 GET Position OK JSON Value parameter found OK
14:04:18.966 GET Position OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:18.966 GET Position OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1282
14:04:18.966 GET Position OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:18.967 GET Position Response: {"ServerTransactionID": 1282, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.969 GET Position OK ServerTransactionID is correctly cased
14:04:18.969 GET Position OK ClientTransactionID is correctly cased
14:04:18.970 GET Position OK ErrorNumber is correctly cased
14:04:18.970 GET Position OK ErrorMessage is correctly cased
14:04:18.970 GET Position OK JSON Value parameter found OK
14:04:18.971 GET Position OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:18.971 GET Position OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1283
14:04:18.971 GET Position OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:18.971 GET Position Response: {"ServerTransactionID": 1283, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.974 GET Position OK ServerTransactionID is correctly cased
14:04:18.975 GET Position OK ClientTransactionID is correctly cased
14:04:18.975 GET Position OK ErrorNumber is correctly cased
14:04:18.976 GET Position OK ErrorMessage is correctly cased
14:04:18.976 GET Position OK JSON Value parameter found OK
14:04:18.977 GET Position OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:18.977 GET Position OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1284
14:04:18.978 GET Position OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:18.978 GET Position Response: {"ServerTransactionID": 1284, "ClientTransactionID": 67890, "Value": 0.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:18.980 GET Position OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:18.980 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.982 GET Position OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:18.983 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:18.989 GET Position OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:18.989 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:18.994 GET Position OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:19.003 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:19.005 GET Position OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:19.006 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.007 GET Position OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:19.008 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.010 GET Position OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:19.010 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:19.013 GET Position OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:19.013 GET Position Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:19.015 GET Reverse OK ServerTransactionID is correctly cased
14:04:19.016 GET Reverse OK ClientTransactionID is correctly cased
14:04:19.017 GET Reverse OK ErrorNumber is correctly cased
14:04:19.018 GET Reverse OK ErrorMessage is correctly cased
14:04:19.018 GET Reverse OK JSON Value parameter found OK
14:04:19.018 GET Reverse OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:19.018 GET Reverse OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1285
14:04:19.019 GET Reverse OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:19.020 GET Reverse Response: {"ServerTransactionID": 1285, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.022 GET Reverse OK ServerTransactionID is correctly cased
14:04:19.022 GET Reverse OK ClientTransactionID is correctly cased
14:04:19.022 GET Reverse OK ErrorNumber is correctly cased
14:04:19.023 GET Reverse OK ErrorMessage is correctly cased
14:04:19.023 GET Reverse OK JSON Value parameter found OK
14:04:19.023 GET Reverse OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:19.024 GET Reverse OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1286
14:04:19.025 GET Reverse OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:19.025 GET Reverse Response: {"ServerTransactionID": 1286, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.027 GET Reverse OK ServerTransactionID is correctly cased
14:04:19.028 GET Reverse OK ClientTransactionID is correctly cased
14:04:19.028 GET Reverse OK ErrorNumber is correctly cased
14:04:19.028 GET Reverse OK ErrorMessage is correctly cased
14:04:19.028 GET Reverse OK JSON Value parameter found OK
14:04:19.029 GET Reverse OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:19.029 GET Reverse OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1287
14:04:19.029 GET Reverse OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:19.029 GET Reverse Response: {"ServerTransactionID": 1287, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.032 GET Reverse OK ServerTransactionID is correctly cased
14:04:19.032 GET Reverse OK ClientTransactionID is correctly cased
14:04:19.032 GET Reverse OK ErrorNumber is correctly cased
14:04:19.033 GET Reverse OK ErrorMessage is correctly cased
14:04:19.033 GET Reverse OK JSON Value parameter found OK
14:04:19.033 GET Reverse OK Different ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:19.033 GET Reverse OK Different ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1288
14:04:19.034 GET Reverse OK Different ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:19.034 GET Reverse Response: {"ServerTransactionID": 1288, "ClientTransactionID": 67890, "Value": false, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.037 GET Reverse OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:19.037 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:19.040 GET Reverse OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:19.040 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:19.042 GET Reverse OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:19.042 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:19.044 GET Reverse OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:19.045 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:19.047 GET Reverse OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:19.047 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.050 GET Reverse OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:19.050 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.052 GET Reverse OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:19.052 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:19.054 GET Reverse OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:19.054 GET Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:19.061 PUT Reverse OK ServerTransactionID is correctly cased
14:04:19.061 PUT Reverse OK ClientTransactionID is correctly cased
14:04:19.061 PUT Reverse OK ErrorNumber is correctly cased
14:04:19.062 PUT Reverse OK ErrorMessage is correctly cased
14:04:19.062 PUT Reverse OK Parameter Reverse (Good casing) - The expected ClientTransactionID was returned: 67890
14:04:19.063 PUT Reverse OK Parameter Reverse (Good casing) - The ServerTransactionID was 1 or greater: 1290
14:04:19.063 PUT Reverse OK Parameter Reverse (Good casing) - Received HTTP status 200 (OK) as expected.
14:04:19.063 PUT Reverse Response: {"ServerTransactionID": 1290, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.066 PUT Reverse OK ServerTransactionID is correctly cased
14:04:19.066 PUT Reverse OK ClientTransactionID is correctly cased
14:04:19.066 PUT Reverse OK ErrorNumber is correctly cased
14:04:19.067 PUT Reverse OK ErrorMessage is correctly cased
14:04:19.067 PUT Reverse OK Parameter Reverse (Good casing + extra parameter) - The expected ClientTransactionID was returned: 67890
14:04:19.067 PUT Reverse OK Parameter Reverse (Good casing + extra parameter) - The ServerTransactionID was 1 or greater: 1291
14:04:19.067 PUT Reverse OK Parameter Reverse (Good casing + extra parameter) - Received HTTP status 200 (OK) as expected.
14:04:19.068 PUT Reverse Response: {"ServerTransactionID": 1291, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.070 PUT Reverse OK Parameter Reverse (Bad value) - Received HTTP status 400 (BadRequest) as expected.
14:04:19.070 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Bad boolean value \"asduio6fghzz\""}
14:04:19.072 PUT Reverse OK Parameter Reverse (Bad casing) - Received HTTP status 400 (BadRequest) as expected.
14:04:19.073 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Missing, empty, or misspelled parameter \"Reverse\""}
14:04:19.075 PUT Reverse OK ServerTransactionID is correctly cased
14:04:19.075 PUT Reverse OK ClientTransactionID is correctly cased
14:04:19.075 PUT Reverse OK ErrorNumber is correctly cased
14:04:19.078 PUT Reverse OK ErrorMessage is correctly cased
14:04:19.079 PUT Reverse OK Bad ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:19.082 PUT Reverse OK Bad ClientID casing - The ServerTransactionID was 1 or greater: 1292
14:04:19.096 PUT Reverse OK Bad ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:19.097 PUT Reverse Response: {"ServerTransactionID": 1292, "ClientTransactionID": 67890, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.099 PUT Reverse OK ServerTransactionID is correctly cased
14:04:19.099 PUT Reverse OK ClientTransactionID is correctly cased
14:04:19.100 PUT Reverse OK ErrorNumber is correctly cased
14:04:19.100 PUT Reverse OK ErrorMessage is correctly cased
14:04:19.100 PUT Reverse OK Bad ClientTransactionID casing - The returned ClientTransactionID was 0 as expected.
14:04:19.100 PUT Reverse OK Bad ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1293
14:04:19.101 PUT Reverse OK Bad ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:19.101 PUT Reverse Response: {"ServerTransactionID": 1293, "ClientTransactionID": 0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.104 PUT Reverse OK ClientID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:19.104 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:19.107 PUT Reverse OK ClientID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:19.107 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value "}
14:04:19.109 PUT Reverse OK ClientID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:19.110 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value -12345"}
14:04:19.112 PUT Reverse OK ClientID is not numeric - Received HTTP status 400 (BadRequest) as expected.
14:04:19.112 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientID value NASDAQ"}
14:04:19.115 PUT Reverse OK ClientTransactionID is empty - Received HTTP status 400 (BadRequest) as expected.
14:04:19.115 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.118 PUT Reverse OK ClientTransactionID is white space - Received HTTP status 400 (BadRequest) as expected.
14:04:19.119 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value "}
14:04:19.121 PUT Reverse OK ClientTransactionID is negative - Received HTTP status 400 (BadRequest) as expected.
14:04:19.122 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value -67890"}
14:04:19.125 PUT Reverse OK ClientTransactionID is a string - Received HTTP status 400 (BadRequest) as expected.
14:04:19.125 PUT Reverse Response: {"title": "Bad Alpaca Request", "description": "Request has bad Alpaca ClientTransactionID value qweqwe"}
14:04:19.127 GET StepSize OK ServerTransactionID is correctly cased
14:04:19.128 GET StepSize OK ClientTransactionID is correctly cased
14:04:19.128 GET StepSize OK ErrorNumber is correctly cased
14:04:19.129 GET StepSize OK ErrorMessage is correctly cased
14:04:19.129 GET StepSize OK JSON Value parameter found OK
14:04:19.129 GET StepSize OK Good ClientID and ClientTransactionID casing - The expected ClientTransactionID was returned: 67890
14:04:19.130 GET StepSize OK Good ClientID and ClientTransactionID casing - The ServerTransactionID was 1 or greater: 1294
14:04:19.130 GET StepSize OK Good ClientID and ClientTransactionID casing - Received HTTP status 200 (OK) as expected.
14:04:19.130 GET StepSize Response: {"ServerTransactionID": 1294, "ClientTransactionID": 67890, "Value": 1.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.132 GET StepSize OK ServerTransactionID is correctly cased
14:04:19.133 GET StepSize OK ClientTransactionID is correctly cased
14:04:19.133 GET StepSize OK ErrorNumber is correctly cased
14:04:19.133 GET StepSize OK ErrorMessage is correctly cased
14:04:19.134 GET StepSize OK JSON Value parameter found OK
14:04:19.134 GET StepSize OK Good ClientID and ClientTransactionID casing with additional parameter - The expected ClientTransactionID was returned: 67890
14:04:19.135 GET StepSize OK Good ClientID and ClientTransactionID casing with additional parameter - The ServerTransactionID was 1 or greater: 1295
14:04:19.135 GET StepSize OK Good ClientID and ClientTransactionID casing with additional parameter - Received HTTP status 200 (OK) as expected.
14:04:19.135 GET StepSize Response: {"ServerTransactionID": 1295, "ClientTransactionID": 67890, "Value": 1.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.137 GET StepSize OK ServerTransactionID is correctly cased
14:04:19.138 GET StepSize OK ClientTransactionID is correctly cased
14:04:19.138 GET StepSize OK ErrorNumber is correctly cased
14:04:19.138 GET StepSize OK ErrorMessage is correctly cased
14:04:19.139 GET StepSize OK JSON Value parameter found OK
14:04:19.139 GET StepSize OK Different ClientID casing - The expected ClientTransactionID was returned: 67890
14:04:19.139 GET StepSize OK Different ClientID casing - The ServerTransactionID was 1 or greater: 1296
14:04:19.140 GET StepSize OK Different ClientID casing - Received HTTP status 200 (OK) as expected.
14:04:19.140 GET StepSize Response: {"ServerTransactionID": 1296, "ClientTransactionID": 67890, "Value": 1.0, "ErrorNumber": 0, "ErrorMessage": ""}
14:04:19.142 GET StepSize OK ServerTransactionID is correctly cased
14:04:19.142 GET StepSize OK ClientTransactionID is correctly cased