+1 for Specflow I like to use BDD through specflow for my automated acceptance tests of major pieces of functionality. These are my integration tests - big, slow, exercise the system from end to end to show that the pieces play nicely with each other. I then move to microtests (often called unit tests) for fleshing out the functionality of the pieces. This outside-in approach is best exemplified in GOOS <http://www.amazon.com.au/Growing-Object-Oriented-Software-Addison-Wesley-Signature-ebook/dp/B002TIOYVW>. The BDD approach *helps *ensure that the system does what it is supposed to do and indicates when done is done. The microtests *support *the creation of easy-to-use code that is SOLID, dependency-light and highly modifiable.
On 1 April 2015 at 11:36, <osjasonrobe...@gmail.com> wrote: > Two .NET BDD tools: http://docs.teststack.net/bddfy/index.html & > http://www.specflow.org/ > > Jason Roberts > Journeyman Software Developer > > Twitter: @robertsjason > Blog: http://DontCodeTired.com > Pluralsight Courses: http://bit.ly/psjasonroberts > > =========================================================== > I welcome VSRE emails. Learn more at http://vsre.info/ > =========================================================== > > *From:* Corneliu I. Tusnea <corne...@acorns.com.au> > *Sent:* Tuesday, 31 March 2015 6:04 PM > *To:* ozDotNet <ozdotnet@ozdotnet.com> > > BDD. http://en.wikipedia.org/wiki/Behavior-driven_development > There is a BDD package for .Net as well. > > Once you learn to write you test out of small bite-size pieces you'll love > it's power. > I hate unit tests. I think they are easy for simple code that is not worth > testing and too complicated to setup for really complicated code. > However once you learn BDD and figure out how to compose tests you can > actually start to test complex components instead of small bits of code. > > > On Tue, Mar 31, 2015 at 11:42 AM, David Burstin <david.burs...@gmail.com> > wrote: > >> Xunit, moq, resharper, ncrunch, fluentassertions >> >> On 31 March 2015 at 09:24, William Luu <will....@gmail.com> 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 <will....@gmail.com> 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 <tonyw...@gmail.com> >>>> 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 >>>> >>> >>> >> >
