Univention Bugzilla – Bug 40032
Validate App metadata on integrity
Last modified: 2016-10-21 18:50:31 CEST
There should be automated tests that check the app metadata on integrity. There are the .ini and .meta files. Both have attributes. The checks should include the following: 1) All mandatory attributes are defined in the metadata. 2) References to files like logos or app appliance images should check for existence of the files. 3) Links should be checked that they are available There may be more checks useful. Please add appropriately.
(In reply to Nico Gulden from comment #0) > 1) All mandatory attributes are defined in the metadata. Which attributes are mandatory for the files in order to match the website requirements?
(In reply to Stefan Gohmann from comment #1) > (In reply to Nico Gulden from comment #0) > > 1) All mandatory attributes are defined in the metadata. > > Which attributes are mandatory for the files in order to match the website > requirements? For the App catalog the following attributes are needed: * .ini: ID, Name, ShortDescription, Description, Version, Website, Thumbnails, Vendor, VendorWebsite, Maintainer, MaintainerWebsite, Contact, SupportOptions, LogoDetailPage * .meta: ID, DetailpageOnCatalogue, TeaserpageOnCatalogue, UniventionApp
We already have some checks: $ grep desc: ucs-test/tests/20_appcenter/1?_check_apps_ini* ucs-test/tests/20_appcenter/10_check_apps_ini:## desc: Simple check if App's .ini(s) can be used. ucs-test/tests/20_appcenter/11_check_apps_ini_field_values:## desc: Check if App .ini has values in settings that are present. ucs-test/tests/20_appcenter/12_check_apps_ini_all_fields:## desc: Checks Apps .ini field values, description length, optional values. IMHO they should be moved to some "pre-publish-to-app-center" stage instead of every ucs-test instance checking the same ini files again and again.
(In reply to Philipp Hahn from comment #3) > IMHO they should be moved to some "pre-publish-to-app-center" stage instead > of every ucs-test instance checking the same ini files again and again. No, we should better use ucs-test for this because we will send the ucs-test output to the ISV. So, the ISV can re-check the ini file.