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've searched existing issues and found nothing related to my issue.
Describe the bug
It seems that if a test fails due to a syntax issue (for example, an unrecognized command in Bruno), Bruno does not take this test into account in the counting of failed tests. Is there a reason behind it? Could you include this type of failure in the counting of test failures (KO)?Thanks
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered:
Hi @Az-aj , the failing tests should reflect in the summary as 'Failed'. I think there could be an error in the scripts which could have thrown the error. Can you check running the collection without scripts and let me know if this issue persists (just want to make sure the error is coming from the tests not the scripts). I understand that the summary of the collection run could be improved in terms of adding different summaries for tests, requests and assertion results. We're working on it.
Hi @sreelakshmi-bruno .First of all,thanks for your response.
No, the Script part of my test was empty. I'll give you another example (see the screenshots) where there's an issue in the test because Bruno doesn't recognize the 'responseBody' object (retrieved from Postman).When I ran the collection, the first test, for example, failed because there is an issue to fix in the test part. However, this test was not counted in the summary as failed.
Maybe it would be better to display it as failed (KO) so that we could know that there's a test to fix?
I have checked the following:
Describe the bug
It seems that if a test fails due to a syntax issue (for example, an unrecognized command in Bruno), Bruno does not take this test into account in the counting of failed tests. Is there a reason behind it? Could you include this type of failure in the counting of test failures (KO)?Thanks
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered: