Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Failed due to a syntaxe issue #3667

Open
2 tasks done
Az-aj opened this issue Dec 16, 2024 · 3 comments
Open
2 tasks done

Test Failed due to a syntaxe issue #3667

Az-aj opened this issue Dec 16, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Az-aj
Copy link

Az-aj commented Dec 16, 2024

I have checked the following:

  • I use the newest version of bruno.
  • 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

tests failed bruno

@Az-aj Az-aj added the bug Something isn't working label Dec 16, 2024
@sreelakshmi-bruno sreelakshmi-bruno self-assigned this Dec 17, 2024
@sreelakshmi-bruno
Copy link
Collaborator

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.

@Az-aj
Copy link
Author

Az-aj commented Dec 18, 2024

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?
Bruno 1 (failed)
Bruno 2 (failed)

@sreelakshmi-bruno
Copy link
Collaborator

Thanks for sharing more details, we're looking into it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants