# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 19362 | tjuricek |
Initial approach to running an upgrade, which basically gets past one stupid issue where the trust files already exist. This is likely not going to be how we exactly test. We'll probably want to run some before and after verifications, for example, to modify configuration and ensure it isn't touched during upgrades. But it's a starting point for further work. |
||
#1 | 19338 | tjuricek |
Create custom reporting mechanism to allow for clear "multiple suite" reports... with logging! This standardizes on log4j 2 as the backend (was just used on the server side). We have an "in memory appender" that we use to capture results during testing, which we associate with each method run. The whole system spits out yaml files for each suite run, which are then read in via a final task and a single html report is spit out with ... everything... in it. |