Guy kolbis

In the following cast, I will be talking about the transactions for both unit tests and web tests. Transactions specifies one or more steps that are grouped together, in the web test context those steps are a bunch of URLs, where in unit test it is a bunch of code that is marked as a group.

So, why do we need it?

I will try and explain it using an example. Lets say that you have a really complicated scenario that must be executed within a unit test. The scenario requires a long initialization and couple of calls to the CRM service and to the Billing service. Because the initialization and the calls are located in the same unit test method, by default the statistics such as response time will be collected for the entire test method, however we would like to get statistics only for the calls (without the initialization) and we also would like the response time for each call and not just the total.

In this cast, I will explain the way to achieve that.

You can download it from here.