[This message was posted by James Downs of Connamara Systems, LLC 
<[email protected]> to the "General Q/A" discussion forum at 
http://fixprotocol.org/discuss/22. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/307ed662 - PLEASE DO NOT REPLY BY MAIL.]

Being in on the "ground floor" of QuickFIX we naturally leveraged and enhanced 
the QuickFIX acceptance framework. Now after several years and many, many 
projects have the ability to automate repeatable functional testing of entire 
trading platforms including market-data driven applications. It is basically, 
FIX in expected FIX out (the i an e). We have also extended the frame work to 
non-fix protocols. So our experience is that the QuickFIX acceptance test 
runner is a good starting point for creating a full functional testing 
framework for FIX enabled applications.

  However as you mentioned that task of creating the tests as they are is 
laborious and error prone (believe me I've written so many of these tests I 
know). We have made a few attempts at creating a higher level language to 
create the tests but thus far those attempts have fallen short. We currently 
have an internal project to use the QuickFIX data dictionary to drive a UI. So 
we too are interested in the experience of others.
Jim






> Hi:
> 
> We're exploring ways to automate our function testing in FIX. So I
> thought I could borrow from this forum's collective intelligence:
> 
> "How do you do your functional testing? Off-the-shelf tools? Custom
> built tools? Simpel scripts?"
> 
> Thanks for your time!


[You can unsubscribe from this discussion group by sending a message to 
mailto:[email protected]]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/FIX-Protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to