feat(logs): log teststep output vars in case of failure#837
Merged
Conversation
ebd2a83 to
4daed5c
Compare
yesnault
requested changes
May 2, 2025
yesnault
approved these changes
May 5, 2025
Collaborator
|
CDS Report build-venom-a#275.0 ✘
|
Signed-off-by: alexGNX <alexandre.gagneux12@gmail.com>
peczenyj
pushed a commit
to peczenyj/venom
that referenced
this pull request
May 7, 2025
Signed-off-by: alexGNX <alexandre.gagneux12@gmail.com> Signed-off-by: Tiago Peczenyj <tpeczenyj@weborama.com>
ceriath
pushed a commit
to ceriath/venom
that referenced
this pull request
Jul 11, 2025
Signed-off-by: alexGNX <alexandre.gagneux12@gmail.com>
storagebits
pushed a commit
to storagebits/venom
that referenced
this pull request
Apr 17, 2026
Signed-off-by: alexGNX <alexandre.gagneux12@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Troubleshooting teststep failures is often cumbersome, especially when using User Defined Executors.
E. g., let's take the simple case of a failure on a teststep using the
httpexecutor. You need details to understand why the tested API doesn't responded as expected, so you want to have a look to the detailed output of the executor, in that case to analyze the response body and headers for example.To do that, one option is to add the
infokeyword in the teststep, like:This is useful but has a couple of issues:
infokeyword is not working if you use it on a testcase inside an UDE.This change is simply about adding all this info into the log, when a failure occurs.
It also changes the log level of passing teststeps from
WarntoInfo.Example of the logs it produces: