http://winterdom.com/2007/08/pipelinetesting11released by dæmons be driven Tue, 16 Mar 2010 06:33:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://winterdom.com/2007/08/pipelinetesting11released/comment-page-1#comment-1302 Unit Testing a BizTalk Solution: Part I « Whiteboard Works Tue, 02 Feb 2010 03:39:19 +0000 http://winterdom.com/2007/08/pipelinetesting11released#comment-1302 [...] and executed. That’s exactly where Winterdom Pipeline Testing Framework enters in scene; see (Restrepo, 2007) for more details. Winterdom Pipeline Testing Framework will provide support to execute pipelines as [...] [...] and executed. That’s exactly where Winterdom Pipeline Testing Framework enters in scene; see (Restrepo, 2007) for more details. Winterdom Pipeline Testing Framework will provide support to execute pipelines as [...]

]]> http://winterdom.com/2007/08/pipelinetesting11released/comment-page-1#comment-423 Tomas Restrepo Thu, 23 Aug 2007 14:11:48 +0000 http://winterdom.com/2007/08/pipelinetesting11released#comment-423 Thanks for the kind words, Richard; glad it was useful :) Do let me know if you run into any issues or have any feature requests. Thanks for the kind words, Richard; glad it was useful Do let me know if you run into any issues or have any feature requests.

]]> http://winterdom.com/2007/08/pipelinetesting11released/comment-page-1#comment-422 Richard Thu, 23 Aug 2007 10:16:35 +0000 http://winterdom.com/2007/08/pipelinetesting11released#comment-422 I spent 45 minutes trying to the out-of-the-box pipeline test components working for and got nowhere. Downloaded YOUR bits, and accurately tested my pipeline in about 10 minutes. You my friend, are the hero of the day. I spent 45 minutes trying to the out-of-the-box pipeline test components working for and got nowhere. Downloaded YOUR bits, and accurately tested my pipeline in about 10 minutes. You my friend, are the hero of the day.

]]> http://winterdom.com/2007/08/pipelinetesting11released/comment-page-1#comment-421 Tomas Restrepo Thu, 09 Aug 2007 15:16:55 +0000 http://winterdom.com/2007/08/pipelinetesting11released#comment-421 Chris, First of all, thanks for the kind words; it's great to know of other people using it. If you have other improvement requests do let me know! As for your specific issue; yes, it is correct to say that I'm forcing UTF-16 encoding when creating a message from a string; and to be honest, it was intentional. The class does the right thing, actually and also sets the Charset property of the Body Part according to the spec; and that's why it works perfectly with the standard disassemblers. If you're writing a custom disassembler, then you should *definitely* be using the Charset property to find out what the encoding of the message is (if it's not present, use a sensible default like UTF-8). Chris,
First of all, thanks for the kind words; it’s great to know of other people using it. If you have other improvement requests do let me know!
As for your specific issue; yes, it is correct to say that I’m forcing UTF-16 encoding when creating a message from a string; and to be honest, it was intentional. The class does the right thing, actually and also sets the Charset property of the Body Part according to the spec; and that’s why it works perfectly with the standard disassemblers.
If you’re writing a custom disassembler, then you should *definitely* be using the Charset property to find out what the encoding of the message is (if it’s not present, use a sensible default like UTF-8).

]]> http://winterdom.com/2007/08/pipelinetesting11released/comment-page-1#comment-420 chris restall Thu, 09 Aug 2007 15:07:07 +0000 http://winterdom.com/2007/08/pipelinetesting11released#comment-420 Hi Tomas, Really great testing utility. I plan to use it extensively. I did run into a small bug though. I am trying ot unit test a simple XML disassembler component and am using basically the following code to create my message: MessageHelper.CreateFromString("<root><order></order></root>") Everything works well except in my disassembler code, I use an XmlTextReader() to do some work on the incoming message. It fails loading the message as the IBaseMessage Arrives like this: < r o o t > < o r d e r > < / o r d e r > < / r o o t > This appears to be due to the CreateFromString method using Unicode to get the byte content. I remedied this by adding an overload that allows for specifying the encoding to use on message creation. CreateFromString(string body, Encoding encoding) In the integration tests, I can simply add the appropriate decoder component to the pipeline and avoid having to worry about the encoding. Again, Thanks for a really useful utility Hi Tomas,
Really great testing utility. I plan to use it extensively. I did run into a small bug though. I am trying ot unit test a simple XML disassembler component and am using basically the following code to create my message:
MessageHelper.CreateFromString("<root><order></order></root>")
Everything works well except in my disassembler code, I use an XmlTextReader() to do some work on the incoming message. It fails loading the message as the IBaseMessage Arrives like this:
< r o o t > < o r d e r > < / o r d e r > < / r o o t >
This appears to be due to the CreateFromString method using Unicode to get the byte content. I remedied this by adding an overload that allows for specifying the encoding to use on message creation.
CreateFromString(string body, Encoding encoding)
In the integration tests, I can simply add the appropriate decoder component to the pipeline and avoid having to worry about the encoding.
Again, Thanks for a really useful utility

]]>