ISV Compliance Tutorial

Installation

1. Download the Moblin Application Checker package from the Moblin Compliance page. The working scenario depends on the variant you downloaded.
   • Installable package.
     1. Install the package using the rpm or dpkg package manager (with root privileges), depending on the package you downloaded:rpm -i moblin-app-checker-<version>.<architecture>.rpmordpkg -i moblin-app-checker_<version>_<architecture>.deb
     2. Start the Moblin App Checker by running the script:/opt/moblin/app-checker/bin/app-checker-start.pl [port-number]You may need to enter the root password.
   • Non-installable (local) package.
     1. Unpack the package:tar xzf moblin-app-checker-local-<version>.<architecture>.tar.gz
     2. Start the Moblin App Checker by running the script:./moblin-app-checker/bin/app-checker-start.pl [port-number]The App Checker will be running with the current user's privileges.
2. This script will start a simple web server embedded in the Moblin App Checker and will try to locate and open your web-browser with the proper address for this server. There is also a script for stopping the server (see below for details).
3. Notes:
   • The port-number argument is optional (by default 8890 is taken). You can use it if port 8890 is already taken by some application.
   • If the script could not find your web-browser and you wish to use Web-UI, please start the browser manually and specify the address http://localhost:8890/ (the port number should be the same as specified on the previous step).
   • You may also connect to the Moblin App Checker from any remote computer by specifying the URL http://<test-machine-name>:8890/ in your web-browser. To enable this feature, you should modify the AcceptConnections key in the server configuration file (/etc/opt/moblin/app-checker/app-checker-server.conf for the installable version and in ./config/app-checker-server.conf for the non-installable one), and then restart the server.

Using Web-UI

1. In the browser you will see the main page of the Moblin App Checker.
2. To specify the application to test, open the Application Check page. You can see the following options there:
   
   You should specify the name of the application and all application binaries (both executable and libraries supplied with the application) to test. Using the Choose Application Components dialog, you can select the necessary files, as well as directories with all their contents, packages (RPM, DEB, TAR.GZ, TAR.BZ2 are supported) and installed RPM or DEB packages (depending on your system). There is also the expandable Additional options block where you can specify the Moblin version to check against, and specify some comments for the test run (e.g. to distinguish it from other test runs). (The Architecture field present in this block currently cannot be changed and is reserved for possible future use.) After specifying all the parameters, press the Run the Test button.
   Note: There are some prerequisites for the test suites to be able to run (listed in the <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.
3. The test will be executed and you will be redirected to the Test Report page. It contains the exhaustive information about the test run. You can group the test results either by component, or by problem category:
      
   For completing the test run, manual tests should also be executed. You can open the Manual Tests page by clicking the link in the red box.
   
   This page represents the set of Yes/No questions. Also, if automated tests produced some FIP results (which stand for Further Information Provided and are generated when some checks cannot be performed automatically), these will be shown on this Manual Tests page. You need to check whether specific requirements are met and answer the questions. After that press the Finish button at the bottom of the page, and you will be redirected to the updated Test Report page.
4. The list of all the reports generated for every test run is shown on the Results History page:
   
   To view any particular report, just click the corresponding link in the Date/Time column. To remove some of the reports, just select them with the check boxes and press the Remove Selected Entries button.

Using Command Line UI

Instead of using the web-based interface, you may use the command-line interface.

1. Go to the directory /opt/moblin/app-checker/utils for the installable version and to ./moblin-app-checker/utils for the non-installable one.
   • Execute the command:./run_tests.pl --paths=<paths-list>where <paths-list> is a colon-separated list of files or directories to be tested.
   • For testing the contents of the packages installed on your machine, you can use the following command:./run_tests.pl --packages=<packages-list>where <packages-list> is a colon-separated list of package names.
2. In addition, the following options may be useful:
   • -n : Name of the application.
   • --moblin=<Moblin-version>: Explicitly specify the Moblin compliance specification version to test against (default is 2.0).
   • -r <results-dir>: Specify the directory for the results.
3. Please see./run_tests.pl --helpfor the full list of the options available in the current version.

Test Results Repository

The results for test runs are stored in the directory /var/opt/moblin/app-checker/results for the installable version and in ./moblin-app-checker/results for the non-installable one. All the files from each test run are stored in separate subdirectories named <arch>-<machine>-<application>-<date>-<time>. For the result to be visible on the Results page of the Web-UI it should be listed in the …/results/HISTORY file.

If you are using Web-UI for running the tests, the HISTORY file is managed automatically. If you copy the test results from another machine or another directory by hand, you will need to write the directory names into this file manually.

Stopping

• To stop the web-server, go to the Administration page in the web-interface and press the Stop server button. Alternatively, you may run the script<app-checker-dir>/bin/app-checker-stop.pl [port-number]The port number is optional and can be used when there are several App Checker servers running on the same machine (if in this case you do not specify the port number, you will be asked for it).

Uninstalling

• If you wish to uninstall the installable Moblin App Checker version, use your package manager (rpm or dpkg) to remove the package moblin-app-checker:rpm -e moblin-app-checkerordpkg -r moblin-app-checkerAfter that you may also wish to delete the old results, logs and other data from the /var/opt/moblin/app-checker directory.
• To uninstall the non-installable Moblin App Checker version just remove its directory.
  Warning: this directory contains not only the App Checker, but also all your test results!