You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have my doubts about this one. The goal of the output section is to provide a concise and user-friendly short message to the user to inform her of the overall result. I'm afraid if we add support for multiple messages this could be abused by e.g. listing a long set of errors as individual messages. Keep in mind also that this message figures also in PDF reports and tooltips, meaning that it should not be something too extensive. There is also a technical challenge here, given that the output conditions are applied in sequence and will stop when a condition match is successful. This allows you to check in sequence for conditions and stop on the most accurate match, avoiding multiple incorrect matches if you would continue to check all conditions.
If you need to create a more complete report with custom outputs for the user you could potentially find useful the DisplayProcessor. This is a processing handler that allows you to pass any set of inputs to create a customised report. You could for example construct this at the end of a test session to show multiple sets of feedback (although this would not be executed if you've set the test case to stop on errors).
To better understand your needs could you explain how you envisage using multiple output messages?
Hello @costas80,
We have started to integrate output messages in our tests. However we would want to display multiples messages for a single testcase.
Do you think it would be possible to implement that one day?
The text was updated successfully, but these errors were encountered: