Having learned what the Linux Application Checker (“AppChecker”) can do, it's now time to install and implement AppChecker. This document describes general steps on getting started with AppChecker, from installation to execution to interpreting the results.
* Installing AppChecker\\
* Using the Web Interface\\
* Using the Command Line Interface
* Managing the Test Results Repository
* Administering AppCheck
Download the Linux Application Checker tarball (tar.gz) package for your architecture from the LSB download page. AppChecker runs as non-installed Perl script, which allows you to run AppChecker as a non-root user. To install AppChecker:
tar xzf Linux-app-checker-local-<i><version>.<i><architecture>.tar.gz
AppChecker will run with current user's privileges.
This script will start a simple web server embedded in the Linux Application Checker and will try to locate and open your web browser with the proper address to this server.
<i>port-numberargument is optional (by default
http://localhost:8889/(the port number should be the same as specified on the previous note).
http://<i><test-machine-name>:8889/in your browser.
Using the Web Interface
Once the Linux Application Checker is started, the main page for the web-based application will be displayed in your default web browser. To run your first test, follow these steps:
> Note: The Components field should contain all components of the application: * Individual files
* Whole directories
* Installed RPM packages (prepended with pkg:)
* RPM and DEB package files
* TAR.GZ and TAR.BZ2 archivesThe archives will be automatically unpacked. Only the files of the following type will be tested: * ELF (executables and shared objects)
* Perl scripts
* Python scripts
* Shell scripts
> Note: There are some prerequisites for the test suites to be able to run (listed in the
<i><Linux-app-checker dir>/README file). If they are not met, an error message will be shown at the top of the page when you try to run the tests. In this case you will have to eliminate the problems and run the tests again.
Using the Command Line Interface
You can also, if you prefer, use the command line to run Application Checker tests. To run your first test, follow these steps:
<i><paths-list> is a colon-separated list of files or directories to be tested (the same as Files and directories textbox in the web interface).
- You can use the following command for testing the installed packages:\\ '' ./run_tests.pl --packages=<i><packages-list> ''\\ where ''<i><packages-list>'' is a colon-separated list of package names.\\ \\ In addition, the following options may be useful:
-n <i><name>: Name of the application.
–lsb=<i><LSB-version>: Allows to explicitly specify the LSB version to test against.
-T <i><profile>: Allows to specify the LSB profile to test against. Possible values are: core,c++ and core,c++,desktop (default).
-r <i><results-dir>: Specify the directory for the results.
for the full list of the options available in the current version. Managing the Test Results Repository
./linux-app-checker/results. All the files from each test run are stored in separate subdirectory named
<i><arch>-<i><machine>-<i><application>-<i><date>-<i><time>.<br /><br />
<i><linux-app-checker dir>/bin/app-checker-stop.pl <i>[port-number]The port number is optional and can be used when there are several Linux Application Checker servers running on the same machine (if you do not specify the port number when multiple AppCheckers are running, you will be asked for the port number).
If you haven't done so already, visit the //LSB download page// to download the AppChecker.