When deploying automatically pick newly created Run Configuration

Another pretty esoteric issue…

I’ve been caught by this multiple times leaving scratching my head - why theres not enough coverage?
Say

I select Run Specified Tests,
then click Manage Apex test suites…
create + to create new suite, select tests I need, click OK
Expected: new suite is selected
Actual: whatever was there before

Aside from this, does Connection in Run Configuration matter? Say I want to deploy to production - I create new configuration but forget to select production. IIRC some tests wouldn’t run in such case. I think I might have been caught by this few times too - could we add some validation warning if there is a mismatch?

All of these are part of my qualms with lack of repeatable deployments. I am not sure if you ever faced this and perhaps I should ask in user group first, but - if you don’t have particularly clean workspace, selecting multiple classes, then specifying unit tests each time is cumbersome and error prone. Frequently there’s some missing metadata or coverage issue that requires going back and re-selecting classes and tests from scratch. Would it be possible to re-run deployment (while including changes I might have made in file payload)?

‌

Comments (3)