Of of course, I meant t/modperl/merge.t and module2url Got perl on the brain.
After another look at things like t/merge.t, it looks like there are at least 2 different use cases for module2perl.
1) The $module sent to module2perl will be sent to ::module() and will be the same as the path. This is your first example:
Foo::Bar => /Foo__Bar
2) The $module sent to module2perl will be sent to ::module(), but a DIFFERENT path is required; like in merge3.t where the path == '/merge3/ != TestModperl::merge
What about make mopdeul2url have a hashref as the second arg in which we can override $path, and of course $scheme
Apache::TestRequest::module2path('TestModePerl::merge', { scheme => 'https', path => '/merge3/ }
Of course it should take the necessary precautions for when / is and isn't included, etc.
-=Chris
