Feature #9924
Updated by Ian Colle over 9 years ago
Currently we have no easy way to understand what steps a particular test case does until we look through thru yaml files code and do a memory refresh or reconstruct steps from there. The current description looks like this: <pre> description: upgrade:dumpling-firefly-x:stress-split/{00-cluster/start.yaml 01-dumpling-install/dumpling.yaml 02-partial-upgrade-firefly/firsthalf.yaml 03-workload/rbd.yaml 04-mona-upgrade-firefly/mona.yaml 05-workload/{rbd-cls.yaml readwrite.yaml} 06-monb-upgrade-firefly/monb.yaml 07-workload/{radosbench.yaml rbd_api.yaml} 08-monc-upgrade-firefly/monc.yaml 09-workload/rbd-python.yaml 10-osds-upgrade-firefly/secondhalf.yaml 11-workload/snaps-few-objects.yaml 12-partial-upgrade-x/first.yaml 13-workload/rados_loadgen_big.yaml 14-mona-upgrade-x/mona.yaml 15-workload/rbd-import-export.yaml 16-monb-upgrade-x/monb.yaml 17-workload/readwrite.yaml 18-monc-upgrade-x/monc.yaml 19-workload/radosbench.yaml 20-osds-upgrade-x/osds_secondhalf.yaml 21-final-workload/{rados_stress_watch.yaml rbd_cls_tests.yaml rgw-swift.yaml} distros/centos_6.5.yaml} </pre> One way to address this and add English words to tests would be to enable test designers to add steps (open text comments) into yaml files and later expose those in pulpito as test results. Say if we had a simple test, it could look like: 0-cluster/start.yaml {steps}: "Create a cluster such and such..." 1-dumpling-install/dumpling.yaml {steps}: "Install ..." 2-upgrade-sequence/upgrade-all.yaml {steps}" "Restart osd and then ..." By combining and displaying the list of {steps} in puplito it may serve as self-documenting feature. 3-workload/{rados_api.yaml rados_loadgenbig.yaml} This can also serve server as a base for test plans for future releases.