in reply to How to structure tests that span several modules

Should I, or can I, break out the other tests into separate files in an attempt to modularize? Or is there a cunning way to run groups of tests from a superior file?
Most people simply alphabetize the test file names so that they run in a particular order.

It sounds like you need to do some things manually between test1 and test2? If so, then use Term::Readkey or some other things of receiving input from the tester that it is time to continue.

So no, I don't think skip is what you want. I think you basically would have: 

0-system_check.t
1-read_user_input.t
2-retest_on_files.t

[download]

Replies are listed 'Best First'.
Re^2: How to structure tests that span several modules
by talexb (Chancellor) on Feb 03, 2005 at 22:01 UTC

    Hmm. Well, now I understand why the test files are numbered -- so they're done in a particular order.

    But I think this doesn't help me with the question that I have about modularizing the files. In addition, The 'retest' on your list would not necessarily include the 'system_check' tests. OK, well, I think I have enough information to go ahead and try this out.

    And I'll use the diag method to inform the user of what's going on and perhaps get them to run some additional tests with parameter values (document ID of a specific test file, for example).

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

[reply]
[d/l]

In Section Seekers of Perl Wisdom