Change Details

There is a problem with us not fully testing the example yet this is one of the things we release and link people too. Not sure what is gives the most bang for the buck here but we should consider doing either of the following. Option 1 should in theory be quite easy to setup. There is already a test_example job on github actions. Option 2 has the nice benefit of maybe making the test configuration a bit less complex, however there might be the downside of the tests running slower and probably requires more refactoring to adapt the current configuration to it. - [] 1. Run the tests (or a subset of them) against the `example/` in CI - [] 2. (Optional) Refactor the tests to use the `example/` folder as the base for testing.

There is a problem with us not fully testing the example yet this is one of the things we release and link people too. Not sure what is gives the most bang for the buck here but we should consider doing either of the following. Option 1 should in theory be quite easy to setup. There is already a [test_example](https://github.com/wmde/wikibase-release-pipeline/blob/main/.github/workflows/built_and_test.yml#L514) job on github actions, however this is currently only testing with silly curl requests. Option 2 has the nice benefit of maybe making the test configuration a bit less complex, however there might be the downside of the tests running slower and probably requires more refactoring to adapt the current configuration to it. - [] 1. Run the tests (or a subset of them) against the `example/` in CI - [] 2. (Optional) Refactor the tests to use the `example/` folder as the base for testing.

There is a problem with us not fully testing the example yet this is one of the things we release and link people too. Not sure what is gives the most bang for the buck here but we should consider doing either of the following. Option 1 should in theory be quite easy to setup. There is already a test_example job on github action[test_example](https://github.com/wmde/wikibase-release-pipeline/blob/main/.github/workflows/built_and_test.yml#L514) job on github actions, however this is currently only testing with silly curl requests. Option 2 has the nice benefit of maybe making the test configuration a bit less complex, however there might be the downside of the tests running slower and probably requires more refactoring to adapt the current configuration to it. - [] 1. Run the tests (or a subset of them) against the `example/` in CI - [] 2. (Optional) Refactor the tests to use the `example/` folder as the base for testing.