The most important enhancements are:
- new message based abstraction for communicating with the mock adapter
- the ability to dynamically set the response in a MockRequestResponseStep
- the ability to promote properties on a per-message base when sending messages to BizTalk
- the ability to validate promoted properties in messages received from BizTalk
The MockMessage type
The new MockMessage class is the new way a message is conveyed to and from the mock adapter. The developer is generally abstracted from its usage directly as the Mock* BizUnit steps take care of the details. However this class will be directly used during validation in receive steps. It comes with several handy properties that will ease the validation logic. These are:
The LambdaValidationStep has beed equipped with a new callback property called MessageValidationCallback. This is intended to be used for assigning to it validation methods which accept a MockMessage instance which will be validated against.
BodyString - the message body as a string
BodyStringBase64 - the message body as a base64 encoded string
BodyStream - the message body as a raw byte stream.
Encoding - the actual encoding of the message
For example validating a message which has XML contents is performed as shown below:
...
var receiveValidationStep = new LambdaValidationStep(){
MessageValidationCallback = (message) => ValidateMessage(message)
}
receiveStep.SubSteps.Add(receiveValidationStep);
...
private bool ValidateMessage(MockMessage message){
...
var xMessage = XDocument.Parse(message.BodyStream);
// Now it is up to the implementer to perform the validation logic on the XDocument
// object representing the message contents
...
}
Dynamically setting the response
This feature gives a developer the ability to set the response content in a MockRequestResponseStep instance dynamically. This comes in handy in a number of scenarios but is especially useful in a de-batch schenario where one step instance handles multiple requests and it is desirable to serve different responses for the different requests. Until now this was not possible. This is achieved in a really convenient way by introducing a new callback property to the MockRequestResponseStep class called ResponseSelector. This property takes a pointer to a method with 2 parameters - a MockMessage instance (new type from this version) and an integer representing the index of the request in a de-batch scenario. The method should return a string representing the path to the file where the contents of the response is to be taken from. This gives complete freedom to the developer to decide in which way a particular response shell be chosen. Two typical scenarios here are:
- index based response - the file path for the response is chosen based on the index of the request message
- content based response - the request message contents is inspected and based on a particular rule against certain value/s the desired response is returned
Here is an example of the index based response selector:
...
[DeploymentItem(@"TestData\OddResponse.xml")]
[DeploymentItem(@"TestData\EvenResponse.xml")]
public void MyTest()
{
var reqRespStep = new MockRequestResponseStep(){
...
DebatchCount = 5,
ResponseSelector = (mockMessage, index) =>
SelectEvenOddResponse(mockMessage, index)
};
...
}
...
private string SelectEvenOddResponse(MockMessage mockMessage, int index)
{
if(index % 2 == 0)
return "EvenResponse.xml";]
else
return "OddResponse.xml";
}
...
As one can see above the snippet implements a response selector that returns path to the OddResponse.xml file when the index is an odd number and EvenResponse.xml for the even indexes. The file name is enough here as it is specified as a DeploymentItem for the test method and will resolve correctly during test execution.
Promoting/Validating properties
Here we are talking not only about adapter properties, but any context property that is recognizable by BizTalk server!
How this can be of help to you and your test cases one may ask? First of all one will be able to mimic more precisely the behaviour of the real adapters that are used in your integrations. For instance a WebHttp adapter is a very good example where it allows you to promote custom properties in the message context when a GET request is received in a RESTful receive location. Or to demote such properties in a send port and assign them to designated parts of the path and query in the URL.
Until now one had to do some tricks in order to achieve this sort of behaviour. For example I have usually ended up in creating a new message schema with its elements mapped to the various custom properties that shall be promoted. But this is not enough - a new receive location with the XmlReceive pipeline was also required as the solution did not have the need to parse the incoming request body as all the services were GET ones. As you can see this is not a good practice as there are suddenly introduced new artifacts only for the purpose of testing. This definitely helped me testing the solution thoroughly and as a result no errors were detected down the life cycle path, but still those artifacts are part of that solution and get deployed to all the environments.
In other circumstances you would perhaps need to have a specific adapter or system property promoted in your message context in order for your solution to work as expected. The new feature allows you to promote more than 200+ such context properties in a very convenient way.
The promotion itself is performed in a very simple way - in the 2 mock send step types MockSendStep and MockSolicitResponseStep has been introduced a new property called Properties. It is of type dictionary with a string key and string value. The key identifies the property to be promoted in the context of the message once received in BizTalk through the mock adapter.
Promoting custom properties
For promoting custom properties the syntax of the key is following the standard BizTalk notation for a promoted property - <namespace>#<property name>. It is important to mention here that the assembly containing the property schema with the properties promoted this way has to be properly deployed as part of the solution being tested. Otherwise nothing will be promoted to the message context. Example:var sendStep = new MockSendStep {
...
Properties.Add("http://example.com/customprops#MyProp", "SomeValue"),
...
}
Promoting adapter and system properties
Promoting properties of other adapters or BizTalk system properties is performed the same way as above with the only difference being the syntax for the key. For convenience and to avoid lots of typing there has been introduced a namespace prefix approach for identifying the desired property to be promoted. The syntax is following the dot notation - [namespace prefix].[property name]. For instance promoting the MQSeries adapter property MQMD_MsgSeqNumber would look as follows:
var sendStep = MockSendStep {
...
Properties.Add("MQSeries.MQMD_MsgSeqNumber, "10"),
...
};
Links to the complete list of adapter and system properties that are supported can be found at the end of this post. Note that this list is the same for all the different BizTalk versions from 2010 and up and is based on the latest version of BizTalk - 2016. This means that certain properties wont be available for lower versions. This will not cause any trouble for your tests - if a property hasn't been located it simply won't be promoted to the message context and the processing will continue as intended.
Validating promoted properties in received messages
This is the other new addition to TransMock - when messages are received in the MockReceive and MockRequestResponse steps it is now possible to inspect both their content and their context properties. This is achieved in a bit different way compared to the property promotion technique. There is no new Properties dictionary property introduced to the steps. Instead the LambdaValidationStep has been extended with a new validation method signature that receives a parameter of type MockMessage. This is the only supported way of validating both content and context of a message received from the mock adapter. The existing validation method signature in LambdaValidationStep expecting a Stream is still fully supported so no breaking change there. However it is strongly recommended to move over to the new signature as it brings much more value to the table.
Here is an example of how the validation will be performed:
...
var receiveStep = new MockRequestResponseStep()
{
...
};
var receiveValidationStep = new LambdaValidationStep(){
MessageValidation = (message) => ValidateMessage(message)
};
receiveStep.SubSteps.Add(receiveValidationStep);
...
private bool ValidateMessage(MockMessage message)
{
Assert.IsTrue(message.Properties.Count > 0, "No context properties found in message");
// Validating custom property
Assert.AreEqual("101", "http://www.example.com/custprops#UserId",
"UserId property had wrong value");
// Validating system property
Assert.Operation("GetUserById", "BTS.Operation", "Operation property not as expected");
}
...
As seen above there is shown validation of 2 different properties - custom and system one. They follow the exact same naming convention as when promoting properties on inbound messages. Custom properties use the # convention, while system properties use the . convention with namepsace prefix.
System and adapter property reference
Here is the list of links to the reference of the various adapter and system properties that can be promoted in inbound messages or validation in outbound messages:
AppStream - app stream system properties
BTS - biztalk system properties
EDI - EDI properties
EDIV2 - EDI V2 properties
EDIAS2 - AS2 properties
FILE - file adapter properties
FTP - FTP adapter properties
HTTP - HTTP adapter properties
MIME - MIME properties
MQSeries - MQSeries adapter properties
MSMQ - MSMQ adapter properties
MSMQT - MSMQ Transactional adapter properties
POP3 - POP3 adapter properties
ServiceBus - Azure ServiceBus adapter properties
SFTP - SFTP adapter properties
SMTP - SMTP adapter properties
SOAP - SOAP adapter properties
SQL - SQL adapter properties
WCF - WCF adapter properties
WSS - Windows Sharepoint Services adapter properties
Ingen kommentarer:
Legg inn en kommentar