Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can certainly apply a lot of the concepts of TDD and DDD to BizTalk development. </p> <p>You can design and develop around the concept of domain objects (although in BizTalk and integration development I often find interface objects or contract first design to be a more useful way of thinking - what messages get passed around at my interfaces). And you can also follow the 'Build the simplest possible thing that will work' and 'only build things that make tests pass' philosophies of TDD.</p> <p>However, your question sounds like you are asking more about the code-centric sides of these design and development approaches.</p> <p>Am I right that you would like to be able to follow the test driven development approach of first writing a unti test that exercises a requirement and fails, then writing a method that fulfils the requirement and causes the test to pass - all within a traditional programing language like C#?</p> <p>For that, unfortunately, the answer is no. The majority of BizTalk artifacts (pipelines, maps, orchestrations...) can only really be built using the Visual Studio BizTalk plugins. There are ways of viewing the underlying c# code, but one would never want to try and directly develop this code.</p> <p>There are two tools <a href="http://www.codeplex.com/bizunit" rel="nofollow noreferrer">BizUnit</a> and <a href="http://www.codeplex.com/bizunitextensions" rel="nofollow noreferrer">BizUnit Extensions</a> that give some ability to control the execution of BizTalk applications and test them but this really only gets you to the point of performing more controled and more test driven integration tests.</p> <p>The shapes that you drag onto the Orchestration design surface will largely just do their thing as one opaque unit of execution. And Orchestrations, pipelines, maps etc... all these things are largely intended to be executed (and tested) within an entire BizTalk solution.</p> <p>Good design practices (taking pointers from approaches like TDD) will lead to breaking BizTalk solutions into smaller, more modular and testable chunks, and are there are ways of testing things like pipelines in isolation. </p> <p>But the detailed specifics of TDD and DDD in code sadly don't translate.</p> <p>For some related discussion that may be useful see this question:</p> <p><a href="https://stackoverflow.com/questions/256897/mocking-webservice-consumed-by-a-biztalk-request-response-port#271044">Mocking WebService consumed by a Biztalk Request-Response port</a></p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I still use DDD, TDD in BizTalk?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USDavid Hall
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I still use DDD, TDD in BizTalk?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you very much for your answer. I'm glad there are things like BizUnit and the BizUnit extensions out there. I'll give these a shot.
      singulars
      1. PO
      1. USRyan Montgomery
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload