You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To facilitate software testing for new releases, we need a flexible test environment. This environment should include yet-to-be-defined sets of diverse sample projects, processes, workflows, configurations and users. It must be reproducible, preconfigured, and easy to install. Additionally, it should support dynamic creation with parametrizable software versions, allowing configuration of specific development versions of Kitodo.Production such as tags or branches. Furthermore, comprehensive documentation is essential to ensure the usefulness of this environment.
A prerequisite for this is the definition of baseline functionality and standardized sets of sample data by the Community Board.
Expected Benefits of this Development
By establishing a standardized environment, developers and release managers can communicate changes more effectively. Having a preconfigured version of Kitodo.Production simplifies testing for those new to the software. This benefits developers, release managers, and anyone looking to explore or test Kitodo.Production.
In the long run, this environment could serve as the foundation for testing Kitodo.Production's core features. By automating testing against this baseline, it cuts down on the need for manual testing. This means institutions can concentrate on their own customizations, confident that the established environment always works reliably. Moreover, the documentation provided for users can be done via this environment, ensuring seamless integration of software and documentation independent from the institution that is using it.
Description
To facilitate software testing for new releases, we need a flexible test environment. This environment should include yet-to-be-defined sets of diverse sample projects, processes, workflows, configurations and users. It must be reproducible, preconfigured, and easy to install. Additionally, it should support dynamic creation with parametrizable software versions, allowing configuration of specific development versions of Kitodo.Production such as tags or branches. Furthermore, comprehensive documentation is essential to ensure the usefulness of this environment.
Related Issues
A prerequisite for this is the definition of baseline functionality and standardized sets of sample data by the Community Board.
Expected Benefits of this Development
By establishing a standardized environment, developers and release managers can communicate changes more effectively. Having a preconfigured version of Kitodo.Production simplifies testing for those new to the software. This benefits developers, release managers, and anyone looking to explore or test Kitodo.Production.
In the long run, this environment could serve as the foundation for testing Kitodo.Production's core features. By automating testing against this baseline, it cuts down on the need for manual testing. This means institutions can concentrate on their own customizations, confident that the established environment always works reliably. Moreover, the documentation provided for users can be done via this environment, ensuring seamless integration of software and documentation independent from the institution that is using it.
Estimated Costs and Complexity
I estimate the cost as medium as there are already unofficial prototypical solutions (https://github.com/slub/kitodo-production-docker).
The text was updated successfully, but these errors were encountered: