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

Run multiple launch.json test configurations in sequence #71885

ericbiewener opened this issue Apr 7, 2019 · 2 comments


Copy link

commented Apr 7, 2019

A compounds option currently exists for launching configurations at the same time, but this doesn't work for the test suites I'm trying to run (see the configurations starting here). The first configuration runs fine but the second one doesn't appear to correctly launch. Even if it did, I don't think this would be preferable to running tests in sequence since it creates a potentially less accurate integration test environment.

Running configurations in sequence would be an ideal solution. The test output would need to be preserved in the debug console between each suite.

@weinand weinand assigned isidorn and unassigned weinand Apr 7, 2019

@weinand weinand added the debug label Apr 7, 2019


This comment has been minimized.

Copy link

commented Apr 8, 2019

This is a fair feature request. Though it is not on our immediate plane. Thus assignign to backlog.

@isidorn isidorn added this to the Backlog milestone Apr 8, 2019


This comment has been minimized.

Copy link

commented Sep 10, 2019

This would be very useful to me. I have three dotnet core microservices I run which all have a shared dependency and I frequently get errors of

Performance is degraded. This can occur when the same project is built more than once in parallel

I use launch.json with a compound to launch my three webservices and often times one of them will fail and I'll need to launch it manually afterwards. If I could configure the sequence of the items, perhaps with a configurable time delay, i'd be set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.