Need help with dryrun?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

3.8K Stars 291 Forks MIT License 178 Commits 2 Opened issues


:cloud: Try the demo project of any Android Library

Services available


Need anything else?

Contributors list


Try any android library hosted online directly from the command line

downloads npm Android Weekly Codacy Badge Closed


gem install dryrun



Wait a few seconds and the app is now opened on your phone :smiley:

$ dryrun -h
Usage: dryrun GIT_URL [OPTIONS]

Options -m, --module MODULE_NAME Custom module to run -b, --branch BRANCH_NAME Checkout custom branch to run -f, --flavour FLAVOUR Custom flavour (e.g. dev, qa, prod) -p, --path PATH Custom path to android project -t, --tag TAG Checkout tag/commit hash to clone (e.g. "v0.4.5", "6f7dd4b") -c, --cleanup Clean the temporary folder before cloning the project -w, --wipe Wipe the temporary dryrun folder -h, --help Displays help -v, --version Displays the version -a, --android-test Execute android tests

Alternative scenario (if you don't use

  1. Find the github's repository url
  2. Click the
    download zip
  3. Extract the
    zip file
  4. Open Android Studio
  5. Import the project you just downloaded
  6. Sync gradle
  7. Run the project
  8. Choose the device you want to run
  9. Test all you want
  10. Delete the
    project folder
    and the
    zip file
    when you don't want it anymore


  • Private repos can be tested too :smiley:
    $ dryrun [email protected]:cesarferreira/android-helloworld.git
  • No need to cleanup after you test the library.
  • No need to wait for Android Studio to load.


Be aware that

environment variable needs to be set. See more in here

Additionally, on windows in order to use git commands, the following path should be on the environment variable -


Created by

Cesar Ferreira


MIT © Cesar Ferreira

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.