About Distribution Checker
Distribution Checker is a user interface front-end, which wraps all the current LSB/Moblin test suites into a user-friendly “single LSB/Moblin test suite” with unified test management and analysis capabilities. This facilitates test execution and results analysis thus making the LSB/Moblin tests more attractive for upstream developers as well as making certification process technically more inviting.
Start using Distribution Checker
The latest Moblin Distribution Checker release package can be downloaded from here:
Moblin Distribution Checker x86,
LSB Distribution Checker is incompatible with the old DTK Manager, and they cannot be used together. If you have DTK Manager installed on your computer, please, remove it before installing Distribution Checker and delete its data directory /var/opt/lsb/test/manager (backup it if you plan to return back to the old DTK Manager and will need your previous test results and user profiles).
Please read Distribution Checker Getting Started to get an overview of the tool with screenshots for using it smoothly.
The key features of Distribution Checker are:
- Support for both LSB and Moblin standards.
- Integrated user interface for all the test suites:
- web based;
- command line.
- Selection of tests to run (all, manually selected subset, predefined subsets, etc.).
- Flexible selection of test suite versions and fine tuning of installation and running of each test suite.
- Automatic download of missing test suites from server.
- Advanced progress indication during test run.
- Integration with the LSB Certification System.
- 'One-button' tests execution.
- Global test summary (for all the tests).
- Unified reports in one place.
- Side-by-side comparison of 2 or more test results.
- Manifest-based approach that allows to maintain the list of tests without updating the Distribution Checker itself.
- Improved error handling and reporting.
The following features can be included in the future (note: this is a wish list only - it will be continually supplemented while it is not guaranteed that all the features below will be ever implemented):
- Waiver detection should be synchronized with a centralized online DB of waivers.
- Build mapping between individual tests within LSB test suites and particular interfaces they test (or even particular assertions in the specifications). Given simple support in the test suites, this will allow the following:
- Consolidated reports grouped by various criteria (by test suite, by target library, by specification section (libgroup), by interface, etc.).
- Coverage reports:
- list of tested/untested interfaces (with groupping and summaries);
- list of tested/untested specification assertions (with groupping and summaries). This also can be presented as a colored specification where colors denote if each line in the specification is tested or not by the tests.
- Links in the reports to the Specification’s text (e.g. pointing out for a fail which citation from the specification was actually violated).
- Exhaustive cross-linking of all the reports and related info like specification, documentation and online DB of waivers.
- Ability to re-execute only those test cases that failed at the previous run.