Property talk:P2992
Jump to navigation
Jump to search
Documentation
software quality assurance
quality assurance process in place for a particular software
quality assurance process in place for a particular software
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “software (Q7397), compression algorithm (Q2755432), communication protocol (Q132364)”: item must contain property “instance of (P31)” with classes “software (Q7397), compression algorithm (Q2755432), communication protocol (Q132364)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2992#Type Q7397, Q2755432, Q132364, SPARQL
Value type “quality assurance (Q836575)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value quality assurance (Q836575) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2992#Value type Q836575, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2992#Scope, hourly updated report, SPARQLAllowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P2992#Entity types
Just curious, what does that mean? Is it merely a technical functionality of the repository software being used? If yes, why is it a statement on the item for tool and not the item for the repository software?
--- Jura 09:43, 25 September 2016 (UTC)
- In this case it reads in plain english like this: "Among all the techniques that could be used to verify the quality of the Primary Sources Tool software, a process has been put in place to verify that each time a modification is made to the source code of the software it can build and run as if used in a real use case (Continuous Integration). The tests being used are described at this URL and the result of running them are archived at this URL". It is not a technical property of the source code repository although in this case the description of the process is found in the source code repository. An example where the description of the software quality assurance process is described outside of the source repository is http://github.com/ceph/ceph. The description of the integration tests are at http://github.com/ceph/ceph-qa-suite which is a completely separate repository and the results are archived at http://pulpito.ceph.com/. Does that answer your question ? Dachary (talk) 19:11, 28 September 2016 (UTC)