**Current Situation:**
The example test suite really just tests the latest release,Our current test setup is not very well isolated from our build environment and is almost entirely setup through shell scripts while the actual tests and related setup hooks are in the WDIO/Javascript environment. it is weird to have this in the build pipeline.Making the test setup, As soon as we talk about the distribution storyincluding starting of any needed Docker services, `example` should go there.
Dependent on architectural decisions,happen within Javascript in the same environment the tests are ran would empower us to write better tests, as well as to better control the test environment for each suite or spec file run. what happens with the `example` directory and how do we distribute in the future?Ultimately this setup would give us the pieces we need to potentially run our test suite against arbitrary Wikibase installations regardless of our build setup as we do currently with the Example and Upgrade test suites.
**Goal:**
**Acceptance Criteria:**
[] Specifically analyse what it would take to make the `example` and `upgrade` test suites not need their own shell script setup (or minimise it).
The reasons they require their own shell scripts vs also just using `test_suite.sh` is the information to guide this spike.
[] Also dependent on the features of WDIO (8) to see how we can include the shell scripts functionality in js / ts code.