[This message was posted by Aditya Khandekar of Merrill Lynch 
<[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/d4eb30f7 - PLEASE DO NOT REPLY BY MAIL.]

> . The Sell Side behavior will be somewhat specific to what you are
> connecting to. In your example, the outcome will vary between venues,
> and sometimes between vendors connecting to a same venue.
> 
>   There are multiple ways of performing the validation. Here are 2 I saw
>   in the field: 1) Create a core scenario which holds the business logic
>   (send message, receive execution report, ...) and apply different sets
>   of message validation based on which Sell Side you are connecting to
>   2) Generate your scenario off production log files and replay the
>      logic at will.
> 
> 
> > Hi - Thanks for your reply. I was referring mainly to testing sell-
> > side applications of FIX. By functional testing I meant testing of
> > specific business logic in application-level tags as opposed to
> > 'acceptance' or FIX-compliance testing.
> >
> > A very simple example would be: After partially executing 25m out of
> > the total 100m available, does the Execution Report (35=8) have the
> > correct 'size left'? Did the 'size left' adhere to the trade
> > stipulation I had specified?
> >
> > I understand the restrictions of this forum and for the same reason I
> > was most interested in knowing how sell-side implementations have
> > managed their testing efforts. Some personal experiences / testing-
> > practices recommendations / lessons-learnt / FIX-testing-case-studies
> > would be great.
> >
> > Thanks to all those who took time to reply so far.
> >
> >


Simple scripts is what I have seen working effectively most often..
Herez my two cents on this though...

Creating "smart test cases" is far more important. I have seen instances 
wherein enormous effort in testing was done, it gave false sense of comfort and 
what had to break eventually did!

The developer/BA/tester can try and create smart cases - and then "less is the 
new more" in terms of testing efforts..

[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