It would be nice if a file created by a test case could also be saved to artifacts.
Currently the basic role only stores the test case execution log, but if the test creates some additional file in some cases it would be nice if this file could also be saved to artifacts.
Basically allow files created on test-subject to be saved on artifacts on test-runner
test-subject
test-runner
@bgoncalv please add a case that requires this. Describe it why it would be useful, as well as please add words test-runner test-subject. Something something says me you want to pull from test-subject to test-runner, am I right ?
@bgoncalv it would be necessary also add a note to STI.
Metadata Update from @astepano: - Issue assigned to astepano
Example: https://src.fedoraproject.org/rpms/acpica-tools/blob/master/f/tests/badcode/runtest.sh#_20
It would be nice to have an option to save badcode.asl.expected to artifacts.
badcode.asl.expected
Metadata Update from @bgoncalv: - Issue assigned to bgoncalv (was: astepano)
suggested implementation https://pagure.io/standard-test-roles/pull-request/367
Example: https://src.fedoraproject.org/rpms/acpica-tools/blob/master/f/tests/badcode/runtest.sh#_20 It would be nice to have an option to save badcode.asl.expected to artifacts.
A file called badcode.asl.actual is also produced; it would be handy to be able to save these files so I can see what changed. In theory, the command iasl that produces these files should always work the same. In practice, it does not. If this test fails, these two files -- badcode.asl.actual and badcode.asl.expected are somehow different -- and being able to see the difference between these files tells me what needs to be fixed.
Commit 3cdeea16 fixes this issue