Description
As part of reviewing DUNE-DAQ/daqsystemtest#335, Michal mentioned that the 'failure end block' did not give much information about what the problem was when the integtest failed.
This ties in with Eric's suggestion that we convert our assert calls in integtests when problems occur to pytest.fail calls which can provide more useful information than just a boolean (DUNE-DAQ/daqsystemtest#298).
This Issue requests that we use the 3ru_3df_multirun_test to develop this functionality in the log_file_checks that are included in the integrationtest infrastructure. The goal would be to provide some useful information in the 'failure end block' about what the problem was.
Potential impact radius
Medium
Reason for change
The goal of the change would be to make integtest failures more easy to recognize and understand.
Suggested implementations
See DUNE-DAQ/daqsystemtest#298.
Testing suggestions
No response
Anything else?
No response
Description
As part of reviewing DUNE-DAQ/daqsystemtest#335, Michal mentioned that the 'failure end block' did not give much information about what the problem was when the integtest failed.
This ties in with Eric's suggestion that we convert our
assertcalls in integtests when problems occur topytest.failcalls which can provide more useful information than just a boolean (DUNE-DAQ/daqsystemtest#298).This Issue requests that we use the
3ru_3df_multirun_testto develop this functionality in thelog_file_checksthat are included in theintegrationtestinfrastructure. The goal would be to provide some useful information in the 'failure end block' about what the problem was.Potential impact radius
Medium
Reason for change
The goal of the change would be to make integtest failures more easy to recognize and understand.
Suggested implementations
See DUNE-DAQ/daqsystemtest#298.
Testing suggestions
No response
Anything else?
No response