Thanks for that tip. I'm looking forward to learning about TDD in Catalyst/Perl.
I created a course not to long ago about unit testing for a software company and am really sold on it. On 11/10/06, Kieren Diment - [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On 03/11/06, John Napiorkowski <[EMAIL PROTECTED]> wrote: > > You'll find that a lot of dispatched methods in > Catalyst are wrapped in an eval so that it can catch > errors for you. 'eval 99' is referring to spot in the > evaled code. > > I've found that it can be a bit hard to debug what's > going wrong when the DBIx schema classes have errors. > Try checking that all the required modules are loaded > and so forth. Use 'perl -c ...' to to a sanity check > on the syntax. Try paring down the components you are > loading to see if you can ID the missing or troubled > part. > > Start with the DBIx schemas you created, looks like > that is the core of the issue. This is also what test driven development is for :) Have a look at Catalyst::Manual::Tutorial::Testing _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
_______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
