Added pre-request and tests scripts support from Postman Collection

[survivant]

Description

In Postman you can define Pre-request scripts and tests to do when you do a request. Those information are stored in the collection but were not imported by bruno

linked to this feature : [FEATURE] Support Postman pre-request script and tests when Importing collection #710

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• [X ] I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

#hacktoberfest

[mirkogolze]

Hi @survivant,
cool idea. If you have some time you could try to translate some Postman Syntax to Bruno-Syntax.
Like reading and writing variables.
From pm.variables.set(... -> bru.setVar(...

[survivant]

agree. I'll do that in another PR. I'll try to keep them small, so it's easier to merge

[helloanoop]

Merged!

Thanks @survivant !

If you have some time you could try to translate some Postman Syntax to Bruno-Syntax.

@mirkogolze @survivant
This seems to be a bit hard to do read the syntax and transpile the code correctly.
This actually seems to be a great task for an AI to translate. It'd be great to find something that can run locally.
And also provide an option to use OpenAI api to do this conversion (for folks who are ok)

@survivant Another thing also would be good immediately is to just have these scripts imported in Bruno, but every line commented //. This allows the user to gradually migrate the tests and scripts, but also the app not to crash since pm variable is not found.

[fxsth]

Please do not use a non-deterministic solution for a deterministic problem. An AI is not suitable for translating a syntax, that relies heavily on correctness. It may result in rewritten tests that passes, but test the wrong thing, which is even worse than broken tests.

[helloanoop]

@fxsth Sure.

For now, the tests and scripts get imported (and are commented) by default. The user can migrate the tests gradually.

On the AI part, if we go that route, it won't be baked into the app. Will provide an additional cli tool that can automatically read the files and convert the scripts and it's upto the user to vet the correctness looking at the the diff

My personal opinion is that I would use a cli, use an openai key, and have the ai do the majority of the grunt work and I will vet the changes done by the AI. (Note: my collection scripts are not super confidential, so I am fine to send them to openai to do the conversion)