In ba9fcc7058d924d2c9b85ccb1bf5ecc25c9c08ea, we worked around tcms-results's inability to treat None / Skip / etc. as a non-failure state.
In earlier commits, ie. 0816e6156a7797da5098345a7d7200a095c39f40 we at least added the original result to the result name (message), but it would be best if we could just use native Beaker statuses, like before.
In ba9fcc7058d924d2c9b85ccb1bf5ecc25c9c08ea, we worked around
tcms-results's inability to treatNone/Skip/ etc. as a non-failure state.In earlier commits, ie. 0816e6156a7797da5098345a7d7200a095c39f40 we at least added the original result to the result name (message), but it would be best if we could just use native Beaker statuses, like before.
With TCMS gone (also https://github.com/RHSecurityCompliance/contest/issues/151), we can restore the Beaker-native reporting API.
Alternatively, we may just remove it and rely on TMT only.