Page MenuHomePhabricator

Map out Wikibase Suite's Test landscape
Closed, DeclinedPublic5 Estimated Story PointsSpike

Description

Current Situation:
There are multiple test suites involved, before a wikibase suite release is considered "tested".

There are tests for:

  • media wiki (via gerrit CI?)
  • extensions wikibase (via gerrit CI?)
  • extensions living outside WMF e.g. on GitHub (???)
  • WQS ???
  • WQS frontend ???
  • Elastic Search ???
  • MariaDB ???
  • ???
  • manual product acceptance tests T344970

And finally there is the wikibase suite integration test suite.

Goal: we want to be as confident as possible that we are releasing an error-free product

Acceptance Criteria:

  • Clearly document technical details and scope of each of those upstream test suites
  • Identify missing pieces
  • Define the scope and purpose of the wikibase suite test suite (is this "just" intergration tests?, is this more/less?)
  • Document the outcome

[optional] Notes:

[optional] Open Questions:

Event Timeline

roti_WMDE renamed this task from Explicitely define Wikibase Suite's Test Suite intent to Map out Wikibase Suite's Test landscape.Aug 30 2023, 9:36 AM
roti_WMDE updated the task description. (Show Details)
RickiJay-WMDE set the point value for this task to 5.Oct 19 2023, 1:44 PM
Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptOct 23 2023, 11:06 AM

Our current tests are confirming integration of MedaiWiki plugins, and the interoperability of the services we provide. This is valuable, however some higher level "smoke tests" specifically targeting the Docker / Docker Compose setup we distribute should be considered (e.g. confirming the right things happen on start/stop, down/up in a compose setup, updating an image between minor versions of our distribution, etc). These sorts of scenarios are debatably at the heart of our product currently, as we are mostly at this time packaging things into Docker image distributions. Worth nothin is that along with current refactoring of our distribution, we are deprecating our Upgrade test suite which was testing in this area--but ineffectually. The sort of tests I'm thinking about would mostly be putting the services up, checking that everything is healthy and basically responding on the service as expected (a bit deeper than a health check), and then taking them back down--testing for any issues along the way.

also wondering if there's an opportunity here to consider cloud's testing needs.