Testing procedure - chromebrew/chromebrew GitHub Wiki

To test packages manually:

• Execute crew files <package> to make sure files exist and it looks reasonable (count > 0 and no missing file messages).
• Identify the binaries from the package (crew files <package> | grep bin), if any, and attempt to execute (something like <command> -h or <command> -v).
• If there are any libraries, make sure they are installed in the correct (crew const CREW_LIB_PREFIX) directory.
• If there are any manpages, attempt to run man <command> or info <command>. If not working, check if they are installed in #{CREW_PREFIX}/man instead of the preferred #{CREW_PREFIX}/share/man.
• If it is a dependency of other packages, test to make sure the binaries of the other packages still work as expected.
• Uninstall the package and check for any residue left behind. Removing the package should restore to a state exactly as it was before the package was installed.

Tests are simple ruby scripts. To execute them, run ./test_all while in the tests/ directory of your local Chromebrew Git repository.

Here is an example of a simple test to check for dependency loops.

For more information, see #997.