Declarative test framework » History » Version 1
Peter Amstutz, 03/27/2018 09:35 PM
| 1 | 1 | Peter Amstutz | h1. Declarative test framework |
|---|---|---|---|
| 2 | |||
| 3 | h2. Problem description |
||
| 4 | |||
| 5 | Currently, running tests in Arvados means running the monolithic run-tests.sh script. The current script has several problems: |
||
| 6 | |||
| 7 | * Script is long, complex and hard to maintain |
||
| 8 | * Script sets up its own environment to run tests is substantially different from production environment |
||
| 9 | * Setting up the test environment adds overhead, even when there is nothing to do |
||
| 10 | * Definition of setting up and executing tests is separate from the directory containing the component under test. |
||
| 11 | * Related tasks such as building and testing packages are entirely separate. |
||
| 12 | |||
| 13 | h2. Solution |
||
| 14 | |||
| 15 | I think we want a declarative way to describe our components for the purposes of building, testing and packaging. This would provide the metadata necessary to drive a framework which is able to build, test and package each component based on that metadata. |