unit testing - Unittesting Callable Orchestrations -

unit testing - Unittesting Callable Orchestrations -

working biztalk, utilize callable orchestrations (without pipelines) service other orchestrations, giving more flexibility in architecture. unittesting them rather devious. now, utilize seperate application wrapper orchestration (just calling orchestration test) deploy biztalk before unittesting.

does have improve way unittest callable orchestrations? preferrably, have unittest don't need artifacts deploy.

thanks in advance.

it hard reply open question no, reply that not practically possible.

orchestrations tightly coupled biztalk orchestration engine. if want unit test orchestration, need simulate orchestration engine. not easy job. there lot of specifics there have think about, dehydration, serialization, scopes, how messaging , orchestration works, etc..

i taking right steps separating out parts of orchestrations, , not making them direct bound on physical ports. makes testing possible / easier. less connections means less points of error.

i seek limit amount of orchestration work do. utilize orchestration when there no improve (or @ to the lowest degree more testable) alternative.

if can test orchestration , without much effort, deploying, dropping message, , watching results, doing more testing whole suite of biztalk developers. if create process easy, , automate can (deploy, drop file, check expected output) @ to the lowest degree create easier observe regressions.

the goal create testing easy / inexpensive , reliable, easier test not test. way prevent managers saying skip tests, take long. want them asking: can test first?

unit-testing biztalk biztalk-orchestrations