Pex is useful for discovering boundaries that you didn't even know existed in your code. You basically feed it assertions about invariants that should hold and it will check them. Seems useful for algorithmic stuff.
I'm afraid the MbUnit.Pex module isn't documented formally yet (except in the XML docs). This situation is temporary, however, since we have a Gallio / MbUnit Book project underway. In the meantime the best place to look is on my blog: http://blog.bits-in-motion.com/ Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of CVertex Sent: Monday, June 02, 2008 9:59 PM To: MbUnit.User Subject: MbUnit Re: Pex Visual studio Integration and MbUnit Thanks! is this documented anywhere? It works great now, cept I'm now not sure if Pex is going to be really useful. Pex only appears useful for testing pre conditions, or I'm not using it to it's full extent. CV. On Jun 3, 4:18 am, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > Reference the MbUnit.Pex assembly and the [assembly: PexMbUnitPackage] > attribute to your test assembly. > > Jeff. > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On > > Behalf Of CVertex > Sent: Monday, June 02, 2008 7:57 AM > To: MbUnit.User > Subject: MbUnit Pex Visual studio Integration and MbUnit > > Pex looks great, but the visual studio addon keeps generating MsTests > instead of MbUnit tests. Is there an easy way to change this? > > Then, I suppose it's just a matter of running the Pex tests in MbUnit right? > > Regards, > -CV > > -- > RowTest saves lives. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
