+1 for modular [script] programming. Build in terms of modules and standardize your variables. In the future you can drop-in added functionality easy-peasy-lemon-squeezy.
I've read the Wikipedia article for TDD, and it sounds like throwing stuff at a wall to see what sticks. -- Espi On Wed, Apr 23, 2014 at 4:18 PM, Michael B. Smith <[email protected]>wrote: > Webster and I are old-school. > > We do modular programming. > > We don't need no automated testing. :) > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Webster > Sent: Wednesday, April 23, 2014 6:44 AM > To: [email protected] > Subject: [NTSysADM] RE: PowerShell unit testing > > What is TDD? > > > Webster (who has written a "few" PoSH scripts of "decent" size and > complexity) > ________________________________________ > From: [email protected] <[email protected]> on > behalf of Joseph L. Casale <[email protected]> > Sent: Tuesday, April 22, 2014 10:17 PM > To: '[email protected]' > Subject: [NTSysADM] PowerShell unit testing > > For those that have done TDD with PowerShell, what is your experience with > the few > libraries that provide mocking and testing? > > Pester does mocking, often a requirement and the syntax looks decent. > > PSUnit syntax isn't very appealing to me and I don't think it supports > mocking? > > PSTest looks neat with the .net syntax but looks a bit thin on features? > > Opinions? > jlc > > > > > > >
