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

Collection-Tests are accumulating in the runner for requests when using bru.setNextRequest() #3748

Closed
2 tasks done
pH-autotester opened this issue Jan 7, 2025 · 3 comments · Fixed by #3760
Closed
2 tasks done
Assignees
Labels
bug Something isn't working

Comments

@pH-autotester
Copy link

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

When using Collection-Tests in the Runner and the same request is sent more than once with bru.setNextRequest() the Collection-Tests are performed an additional time for each previous use of that request.

(Putting the Test in the Test-section of the request, this doesn't occur)

.bru file to reproduce the bug

Use any Endpoint with the following in the Tests-section of the Collection:
bru.setNextRequest("Temp1") await bru.sleep(1000) test("Status is valid", function() { expect(res.status).to.be.oneOf([200,201]); });
Adapt the bru.setNextRequest() according to your used Endpoint.

Screenshots/Live demo link

image

@pH-autotester pH-autotester added the bug Something isn't working label Jan 7, 2025
@sreelakshmi-bruno sreelakshmi-bruno self-assigned this Jan 7, 2025
@sreelakshmi-bruno
Copy link
Collaborator

Hi @pH-autotester , thanks for reporting. Similar to #3715 but for tests. We're working on this.

@pH-autotester
Copy link
Author

Appears to be fixed with 1.38

@helloanoop
Copy link
Contributor

The CLI fixes for this issue is now available in version v1.38.2

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

Successfully merging a pull request may close this issue.

3 participants