Best unit testing tools

[Tony Wright]

Hi all,

What are people using these days to unit test code dot net code, and if not
visual studio, why?

Regards Tony

Re: Best unit testing tools

[Dave Walker]

Nunit, moq, and resharper runner. Ncrunch if your company will pay for it.
On 30 Mar 2015 23:49, "Tony Wright"  wrote:

> Hi all,
>
> What are people using these days to unit test code dot net code, and if
> not visual studio, why?
>
> Regards Tony
>

Re: Best unit testing tools

[William Luu]

We're reviewing what to use for a new project and I'm leaning towards the
below:

Unit testing framework: xunit (2.0 was recently released)
Mocking: FakeItEasy

Also, take a look at AutoFixture.

See -
https://lostechies.com/jimmybogard/2015/03/24/clean-tests-isolation-with-fakes/


On Mon, Mar 30, 2015 at 21:49 PM, Tony Wright  wrote:

Hi all,

What are people using these days to unit test code dot net code, and if not
visual studio, why?

Regards Tony



-- 
Sent from MetroMail

Re: Best unit testing tools

[William Luu]

Perhaps start from the first post of that series -
https://lostechies.com/jimmybogard/2015/01/29/clean-tests-a-primer/

The author mentions Fixie, which is a fairly new testing framework -
http://fixie.github.io


On 30 March 2015 at 22:23, William Luu  wrote:

> We're reviewing what to use for a new project and I'm leaning towards the
> below:
>
> Unit testing framework: xunit (2.0 was recently released)
> Mocking: FakeItEasy
>
> Also, take a look at AutoFixture.
>
> See -
> https://lostechies.com/jimmybogard/2015/03/24/clean-tests-isolation-with-fakes/
>
>
>
> On Mon, Mar 30, 2015 at 21:49 PM, Tony Wright  wrote:
>
> Hi all,
>
> What are people using these days to unit test code dot net code, and if
> not visual studio, why?
>
> Regards Tony
>
>
>
> --
> Sent from MetroMail
>

Re: Best unit testing tools

[David Burstin]

Xunit, moq, resharper, ncrunch, fluentassertions

On 31 March 2015 at 09:24, William Luu  wrote:

> Perhaps start from the first post of that series -
> https://lostechies.com/jimmybogard/2015/01/29/clean-tests-a-primer/
>
> The author mentions Fixie, which is a fairly new testing framework -
> http://fixie.github.io
>
>
> On 30 March 2015 at 22:23, William Luu  wrote:
>
>> We're reviewing what to use for a new project and I'm leaning towards the
>> below:
>>
>> Unit testing framework: xunit (2.0 was recently released)
>> Mocking: FakeItEasy
>>
>> Also, take a look at AutoFixture.
>>
>> See -
>> https://lostechies.com/jimmybogard/2015/03/24/clean-tests-isolation-with-fakes/
>>
>>
>>
>> On Mon, Mar 30, 2015 at 21:49 PM, Tony Wright  wrote:
>>
>> Hi all,
>>
>> What are people using these days to unit test code dot net code, and if
>> not visual studio, why?
>>
>> Regards Tony
>>
>>
>>
>> --
>> Sent from MetroMail
>>
>
>

Azure status (409) Conflict

[Greg Keogh]

Folks, has anyone here done some industrial strength coding against Azure
Blob and Table storage? I'm migrating some code that uses local files over
to Blobs, as well as some miscellaneous files like user "settings" which
are ideal for Tables. By just abstracting the "files" and "settings" a
little bit you can get some neat results by changing the backing storage to
be Azure.

However, I unpredictably get *(409) Conflict* errors which kill my apps.
They usually happen after deleting a container or table and recreating it
and writing to it, or after deleting many rows or blobs. I quickly found
the MSDN docs do warn you
 that some
operations can take a while to complete in the background. That makes
sense, but has anyone got a good strategy for dealing with this?! I see
some people Sleep loop until the 409 goes away, and others use different
container or table names when they continue processing. The 1st option is
easy but clumsy, the 2nd is superior but you need to rejig your app logic a
bit.

*Greg K*