[ ] GUI test coverage (steps to reach some interface, from there all widgets must be exercised)
[ ] Accessibility coverage (check that all features can be reached using only sound+keyboard, only braille+keyboard, and using a zoomed interface+inverted colors+mouse
[ ] documentation coverage (guide, reference, interactive usage examples with "show me" button, tutorial/blog article explaining how to write the component)
[ ] upgrades of documents to a newer version of the document type
[ ] downgrades of documents to an older version of the document type. The downgraded document should be handled correctly (unknown features are moved / copied around as much as possible, where features are tagged to indicate if they should be unique (don't copy), copied, and so on.
[ ] number of reviews made by humans: for document types, tools, views, algorithms, GUI, documentation, …
[ ] Check for low redundancy in code? Rename all identifiers to x1, x2, x3… (or serialize a symbolic representation of the AST), then compress the source code and see that the compression ratio is not better than a certain threshold.
[ ] subjective measure of code quality / clarity / maintainability, judged by a human
[ ] check for code smells like tight coupling…
[ ] formal proofs expected or possible for some of the above
x1,x2,x3… (or serialize a symbolic representation of the AST), then compress the source code and see that the compression ratio is not better than a certain threshold.