feat: removed result from testcase variables and removed errors warning and info from non verbose runs

[kilianpaquier]

• removed ranged prints on non-verbose runs
• fixed info not interpolating right variable in step X with .result variable (was showing variable from X-1)
• print info before errors: closes Print info in current "step" before assertions #597
• on non-verbose runs, print info only when there're failures: closes Improving error debugging (especially in CI) #595

[yesnault]

LGTM, thank you @kilianpaquier

[yesnault]

revert. Intergration Tests are failing, example: venom run interpolate_once.yml

[kilianpaquier]

revert. Intergration Tests are failing, example: venom run interpolate_once.yml

Yes sorry, didn't see that one. It doesn't work anymore because I removed all .result from testcase variables.

Only the assigned variables (coming from the key 'vars') are present in testcase variables, that's why interpolation.yaml doesn't fail.

In my opinion, .result should be teststep scoped. If .result must be accessed later, then it should be assigned to a variable during the teststep. It is because every step computes a .result and if multiple steps are to compute .result.systemout, all of them would be stored in the testcase variables but only the last one would be used.

In this case, result.systemout should be assign to a variable, and the comparison should be done with it. Just like it's done in interpolation.yaml.

Another possibility is to prefix .result with the teststep name, like it is done on variable in different testcases.

[kilianpaquier]

revert. Intergration Tests are failing, example: venom run interpolate_once.yml

Yes sorry, didn't see that one. It doesn't work anymore because I removed all .result from testcase variables.

Only the assigned variables (coming from the key 'vars') are present in testcase variables, that's why interpolation.yaml doesn't fail.

In my opinion, .result should be teststep scoped. If .result must be accessed later, then it should be assigned to a variable during the teststep. It is because every step computes a .result and if multiple steps are to compute .result.systemout, all of them would be stored in the testcase variables but only the last one would be used.

In this case, result.systemout should be assign to a variable, and the comparison should be done with it. Just like it's done in interpolation.yaml.

Another possibility is to prefix .result with the teststep name, like it is done on variable in different testcases.

Hello @yesnault, what do you think ?