Collection run upgrade - support for custom integration test

berlingoqc commented 2 weeks ago

I have checked the following:

[X] I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add

The collection run feature is pretty simple.

I used to maintain scripts using newman to run specific integration test.

Config file to define the list of request i want to do in the integration test
Add specific variables for all requests and specific only for some. And we use to run them in CI

Mockups or Images of the feature

Create a new folder in bruno collection to store run configuration

`runs/integration-test-1.bru

meta {
    name: Integration test 1
    seq: 1
}

env { // Add a base environment to use
   name: nonprod
}

vars { // Global variables add on top of the base environment
    AGENT_ID: momcorp
}

requests [
    {
        request: AGENT // Folder or specific request
        vars: { // Variable override

        }
    }
    {
        request: AGENT_2
        vars: {

        }
    }
    {
        request: AGENT/Create Agent.bru
        vars: {

        }
    }
]

# run the integration test in the cli
bru run runs/integration-test-1.bru

Its-treason commented 2 weeks ago

If I create a PR with this feature in the opensource edition will it possibly get merged?

While I can't speak for Anoop directly, I'm pretty sure he will not accept a PR for this:

This is a feature to incentive people to buy the golden edition
The Golden Edition source code is proprietary and has its own implementation for this. The Open-source implementation would need to be merged into the golden edition

But this project is MIT licensed, so feel free to fork the project and implement this or any other feature on your own. I kinda did the same with my fork: its-treason/bruno

berlingoqc commented 2 weeks ago

Yes I see, I would like to help with this project but I don't pay for software ever. I can donate money. I would like if the community could add features without consideration of the proprietary code.

I guess it's the caveat of having an offline open-source tool that you want to monetize. You can't make the user pay for a hosting service so you have to make them pay for basic features required for more enterprise need

usebruno / bruno