To elaborate...

    cd ~/repos/mock-sub
    git pull
    # make changes, perhaps bumping one of my
    # own prereq versions
[download]

My Test::BrewBuild software does a lot of things, but a basic run is started out of the current working directory, and runs unit tests of itself and optionally as in the case below, runs all the unit tests of all reverse dependencies against the changed version of the distribution I'm planning on uploading to the CPAN against any and/or all installed versions of Perlbrew (and Berrybrew) perls (you can also remove them all and install any number of them from scratch to have a clean slate for every test if you want). I won't bother getting into the network dispatching capabilities, or the automation aspects.

Here's an example after a random change that clearly broke things for some of the revdeps:

    brewbuild -R

    reverse dependencies: 

    RPi::DigiPot::MCP4XXXX 
    Devel::Examine::Subs 
    PSGI::Hector 
    App::RPi::EnvUI 
    File::Edit::Portable 
    Devel::Trace::Subs

    RPi::DigiPot::MCP4XXXX
    5.10.1 :: PASS
    5.18.4 :: PASS
    5.20.3 :: PASS
    5.24.1 :: PASS
    5.26.0 :: PASS

    Devel::Examine::Subs
    5.10.1 :: PASS
    5.18.4 :: PASS
    5.20.3 :: PASS
    5.24.1 :: PASS
    5.26.0 :: FAIL

    PSGI::Hector
    5.10.1 :: PASS
    5.18.4 :: PASS
    5.20.3 :: PASS
    5.24.1 :: PASS
    5.26.0 :: FAIL

    App::RPi::EnvUI
    5.10.1 :: FAIL
    5.18.4 :: FAIL
    5.20.3 :: FAIL
    5.24.1 :: FAIL
    5.26.0 :: FAIL

    File::Edit::Portable
    5.10.1 :: PASS
    5.18.4 :: PASS
    5.20.3 :: PASS
    5.24.1 :: PASS
    5.26.0 :: PASS

    Devel::Trace::Subs
    5.10.1 :: PASS
    5.18.4 :: PASS
    5.20.3 :: PASS
    5.24.1 :: PASS
    5.26.0 :: FAIL
[download]

Once all tests pass for all reverse dependencies, it's safe for me to upload the new version to CPAN.