MTT can progress for quite a long time before encoutering a fatal error in one of it's modules. It should warn about an upcoming error of this kind, that is, do a quick eval "use Foo.pm; on each of the modules that will be used, and print big warning(s) about ones that are not going to work. This would prevent the scenario where the user has to restart an MTT run that has run for hours due to it dying hours into an otherwise okay run. Maybe MTT should also have an option that would tell it to skip over sections that use problematic modules? This way, MTT doesn't completely abort what could be at least a ''partially'' successful run. (See also #365 - ''warn about unknown INI parameters''.)
MTT can progress for quite a long time before encoutering a fatal error in one of it's modules. It should warn about an upcoming error of this kind, that is, do a quick
eval "use Foo.pm;
on each of the modules that will be used, and print big warning(s) about ones that are not going to work. This would prevent the scenario where the user has to restart an MTT run that has run for hours due to it dying hours into an otherwise okay run. Maybe MTT should also have an option that would tell it to skip over sections that use problematic modules? This way, MTT doesn't completely abort what could be at least a ''partially'' successful run. (See also #365 - ''warn about unknown INI parameters''.)