Are there plans to support auto running test suites of requests?

[davehouser1]

I am trying to get away from Insomnia, but their test framework is decent. However it leaves a lot to be desired.
I like Bruno, its simple and straight forward. Are there plans to make a auto testing framework portion?
Right now Bruno, seems to only have a "test" tab on each request. This is good if you wanted to test one request. However there are a couple problems I am faced with.

• I cant seem to find a way to have Bruno "auto test". What I mean by this is tell Bruno, "run all the requests in this folder, check assertions, and continue to the next test" It seems I can only run one test manually.
• There does not seem to be a simple way to perform async checks. Only sync.
• If I were to create different test cases, for the same request, I need to duplicate the request, and change the test.

How can I arrange specific requests into a test suite and have Bruno run through those tests and assert in a specific ways? Insomnia does this, and I think to some extent Postman does too. Would be great if Bruno did it. If you think this is a good idea, here are some features I think would be great:

• Build a testing framework section for Bruno. This is a separate section from the requests collections.
• Ability to create "unit tests", which is to say a specific request to run, then assert. I think there are modules you can use to allow users to use JavaScript to confirm a test ran properly. You can use frameworks like Mocha framework, and Chai for assertions.
• You can keep the "test" section on each request, however allow a user to make different test assertions for each unit test in their test suite.
• Ability to create test suites, which is an aggregation of unit tests.
• Ability to create test suites of suites, combining suites together.
• Support duplicating unit tests in a suite.
• Support duplicating tests suites.
• Support re-arraigning unit tests in a suite.
• Support for async requests in a given unit test. Just because a request returned a 200OK does not mean the work is complete on the backend. There has to be someway to perform more operations to check if async work is complete. There can be a variety of of ways to assert this. In most cases Iv seen there maybe another address/route that one can check job status of a job.
• Support for access to environmental variables in tests. Or create a "test environmental variable sets" for a suite or suite of suites.
• Show how long each unit test took to complete
• Support to show total time all tests in a suite took to run.
• The number of tests can become cumbersome, add a way to search for each unit test in a suite.
• Ability to "play" or run any unit test along without having to run the whole suite.
• Control if testing should continue or stop immediately if a single test fails.
• Ability to disable tests
• Ability to control async timeout (Chai sets this to a max of 60 seconds, needs to be adjustable)
• Create and export a report. Report includes all tests, pass fail status, time it took, output of failure. Format is up to you, csv, json, whatever you like.

Btw, if any of these features, or problems I bring up above, are not actual problems (there are ways to do them in Bruno) please let me know!

Hope the best for this program. :)