Unit vs. use case/functional testing

on good books on general testing philosophy would also be helpful (I've already got the developer's notebook). Andrew -- Andrew Gianni - Lead Programmer Analyst University at Buffalo, State University of New York Computing and Information Technology / Administrative Computing Services 215 MFAC

Re: Unit vs. use case/functional testing

and simply ensure that the results are what we expect. Is that basically what you were suggesting? Andrew -- Andrew Gianni - Lead Programmer Analyst University at Buffalo, State University of New York Computing and Information Technology / Administrative Computing Services 215 MFAC, Ellicott Complex

Re: Unit vs. use case/functional testing

. Andrew -- Andrew Gianni - Lead Programmer Analyst University at Buffalo, State University of New York Computing and Information Technology / Administrative Computing Services 215 MFAC, Ellicott Complex, Buffalo, NY 14261-0026 716.645.3587x7124 - AIM: andrewsgianni - http://schoolof.info/agianni

Re: Unit vs. use case/functional testing

not the author. Andrew -- Andrew Gianni - Lead Programmer Analyst University at Buffalo, State University of New York Computing and Information Technology / Administrative Computing Services 215 MFAC, Ellicott Complex, Buffalo, NY 14261-0026 716.645.3587x7124 - AIM: andrewsgianni - http://schoolof.info

Re: Is_deeply and closure-driven coderefs

are going to do all that stuff you might as well use DDS to do it, as its much easier, (which is hardly surprising as the Padwalker closure code was specifically written for DDS'es requirements) Cheers, Yve Andrew Gianni Administrative Computing Services Computing and Information Technology

Running individual unit tests with Test::Class???

, but is there some other, easier way to do this that's built into the module? Andrew Andrew Gianni Administrative Computing Services Computing and Information Technology University at Buffalo 215 MFAC, Ellicott Complex Buffalo, NY 14261-0026 716.645.3587x7124

Re: Running individual unit tests with Test::Class???

, * Andrew Gianni [EMAIL PROTECTED] [2006-05-31 15:40]: Is there an easy way to just run that one test method (as well as the startup, setup, teardown and shutdown methods) while I'm working on it rather than running the whole batch? just write a base test class with all your scaffolding methods

Re: Running individual unit tests with Test::Class???

/06 10:55 AM, Adrian Howard [EMAIL PROTECTED] wrote: [apologies to andrew for a dupe - didn't notice it went to perl-qa] On 31 May 2006, at 14:35, Andrew Gianni wrote: Let me start by admitting that I don't know a whole lot about xUnit testing. In fact, using Test::Class is really my first

Is_deeply and closure-driven coderefs

of comparing those would be. Any assistance would be appreciated. Andrew Andrew Gianni Administrative Computing Services Computing and Information Technology University at Buffalo 215 MFAC, Ellicott Complex Buffalo, NY 14261-0026 716.645.3587x7124

Warnings from Devel::Cover/Test::Harness

not directly. Andrew Andrew Gianni Administrative Computing Services Computing and Information Technology University at Buffalo 215 MFAC, Ellicott Complex Buffalo, NY 14261-0026 716.645.3587x7124