For testing any functions in your codebase.pl files, I believe you should be able to create a test script which has use lib '.'; use 'codebase.pl'; -- anything that's automatically run in your code will, I think, be thrown away (unless the return code is not TRUE -- in which case, the use 'codebase.pl' will fail). If there's too much user-interface (prompting for inputs, etc), I don't know how successful the use will be. But assuming it gets past that point, you can then test the functions from codebase.pl in the same way you would test functions from modules. And you can then eventually move those functions into modules.

Alternatively, you could create a new module newmod.pm (for appropriate package names, and directory hierarchy), and add the line use newmod; to codebase.pl. Then, one by one, move functions out of the codebase.pl into newmod.pm; with each function this_fn() that you move, make sure codebase.pl still runs as it used to (with a quick manual test) to make sure it wasn't using a file-lexical that it shouldn't be, and write up the appropriate t/*.t test suite for the function that's moved into newmod.pm. (Often times, you can make the this_fn.t look very similar to calls from your original codebase.pl). Continue this process until the codebase.pl just contains the script, and all the functions are moved to modules where they can be easily tested.