Current situation: wikibase code has its tests and the wikibase suite has also tests. Nevertheless, we have also a "product verification" step where PMs are supposed to manually go through some paths following this sheet. Some of the paths described there are happy paths.
We need to check the current test coverage to identify parts that are not tested and decide whether and which additional tests are needed. We want to be confident about wikibase code as well as the extensions and their integration with wikibase.
Goal:
- all the happy paths within wikibase and the extenstions are covered by automated tests. Only (and only if needed) some exploratory testing that cannot be perfectly covered that way may be left to do manually.
- be as confident as possible that we are releasing an error-free product
- cover with automated testing as many paths as possible
- define which paths (if any) cannot be tested that way and need to be done manually
Acceptance Criteria:
- Generate tickets for improving test coverage
- Thoroughly document any needed manual tests