As part of software development and in preparation for new releases, tests have to be carried out time and again. Although there are now a large number of automated unit and integration tests, many functions can still only be tested manually.
For this purpose, a reproducible, preconfigured and easy-to-install appliance is to be created. This test environment should contain a yet-to-be-defined set of sample documents that are as varied as possible to enable comprehensive test scenarios. However, the appliance must not only be created statically once (e.g. as a Docker container), but must be able to be created dynamically using parameterizable software versions. For example, it must at least be possible to configure which PHP and TYPO3 versions and which Kitodo.presentation development status (branch or tag) is to be used when setting up the environment.
The set of sample documents could possibly be compiled by the Kitodo Community Board and made available by the respective owning institutions. Ideally, the test environment should also have a standard design to make it easier to carry out surface tests.
Related Issues
1177 is a prerequisite for this proposal.
Expected Benefits of this Development
This will primarily benefit developers and release managers, but would also be an easy starting point for just getting familiar with Kitodo.Presentation or trying out the software.
sebastian-meyer
commented
8 months ago
Description
As part of software development and in preparation for new releases, tests have to be carried out time and again. Although there are now a large number of automated unit and integration tests, many functions can still only be tested manually.
For this purpose, a reproducible, preconfigured and easy-to-install appliance is to be created. This test environment should contain a yet-to-be-defined set of sample documents that are as varied as possible to enable comprehensive test scenarios. However, the appliance must not only be created statically once (e.g. as a Docker container), but must be able to be created dynamically using parameterizable software versions. For example, it must at least be possible to configure which PHP and TYPO3 versions and which Kitodo.presentation development status (branch or tag) is to be used when setting up the environment.
The set of sample documents could possibly be compiled by the Kitodo Community Board and made available by the respective owning institutions. Ideally, the test environment should also have a standard design to make it easier to carry out surface tests.
Related Issues
1177 is a prerequisite for this proposal.
Expected Benefits of this Development
This will primarily benefit developers and release managers, but would also be an easy starting point for just getting familiar with Kitodo.Presentation or trying out the software.
Estimated Costs and Complexity
I estimate the cost as medium to high.