Forum Discussion
5 Replies
Sort By
- krenevlaContributorbut this is not usable when you call module which call another module which (for example) checks status of something every second until loop limit is reached. Then there is lot of text in the log and it's pretty hard to find row where it failed. basically more you modularize, test log in gui is less usable :/
- SmartBear_SuppoSmartBear Alumni (Retired)Hi,
Thanks for the suggestion! I have created an change request (SOAP-422) on our issue internal tracking system.
Our UX engineer will have a look at this and probably come back to you with more information.
Regards,
Shadid
SmartBear Sweden - krenevlaContributor
- SmartBear_SuppoSmartBear Alumni (Retired)Hello,
Internal enhancement request SOAP-422 is currently assigned and open. I would suggest for now to use the test case log bottom tab to check which test step failed until this feature request gets implemented.
Regards,
Marcus
SmartBear Support - SmartBear_SuppoSmartBear Alumni (Retired)Hi,
Yes, I understand it is more difficult to check results in that scenario. As I said, there is an internal enhancement request SOAP-422 open to address this issue.
Regards,
Marcus
SmartBear Support