26.3 Feedback: Interface Test Scenarios

Preface: I LOVE, LOVE, LOVE the new Test Scenarios feature within the 26.1+ interface designer - it takes my longstanding wishlist item and implements it more richly still.

Nevertheless I find myself, while using it, having the following pain points / nitpicks, which I hope relevant parties might see here. (I also posted them in my a!ppIdeas feature request, FWIW.)

Issues / wishlist:

• Ability to tell which scenario we're currently ON
  • We are given no clue what scenario (if any) we're currently viewing, whether you look at 
    • The interface designer,
    • the test scenario picker drop-down (which should be a bare minimum)
  • Somewhere, we should be able to see which one we're on and/or which one was most recently selected
    
    
• Ability to reorder the scenarios within the "Manage Scenarios" pop-up
  • if one is selected, give us a "move up / move down" button or something
    
    
• If a scenario is loaded and we click "TEST", the default values seen in the inputs should populate with that scenario (curently populates blank), and that scenario should show by default in the "scenario values" dropdown
  • Corrolary: if a scenario is loaded and then updated from the general "TEST" pop-up, it'd be nice to have an "update and TEST" button as well as the general "TEST" button, similar to when a scenario is updated from the Manage pop-up.
    
    
• "Reset to Default State" button would be better served to revert to the "load state" for the CURRENT SELECTED SCENARIO (if any), rather than resetting to the scenario marked as "Default".  If I need to switch to default I can simply pick it from the "Test" dropdown scenario selector; if I want 1-touch "reset" functionality, 99% of the time it'll be for resetting the thing I'm currently working on (which will usually be the loaded scenario).

Everyone is invited to add your own feedback in the comments if you want, but please keep it RELEVANT and GENERAL (i.e. focused on this feature, and not hyper-specific or niche use cases unlikely to affect many other implementations).