How can we improve Team Services?

Allow to disable the query "Run tests from the last successful build?"

The Tools / Options dialog contains the following settings for running the application:

On Run, when build or deployment errors occur:
"Launch old version", "Do not launch", "Prompt to launch".

If I hit Ctrl-R A to run all tests and the build results in errors, then the following dialog appears:

"There were build errors. Would you like to continue and run tests from the last successful build?"

This is a hassle, in particular when implementing in TDD-style.
It would be very convenient to have the same choice for tests as for application launch:

On Test, when build or deployment errors occur:
"Launch test from the last successful build", "Do not test", "Prompt to test".

68 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    14 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • RPRP commented  ·   ·  Flag as inappropriate

        More than that, running tests from a previous build would definitely be confusing. Period. Why is this option even there at all. Why on earth would anyone want to test code they don't even have any more?

      • Jeff LambJeff Lamb commented  ·   ·  Flag as inappropriate

        Since this isn't possible to disable this popup, here's an AutoHotKey script to automatically close that window:

        ;************************
        ;Automatically say "no" to visual studio failed build errors that prompt to re-run tests from last successful build
        ;************************
        #Persistent
        SetTimer, lookForBuildFailPopup, 100
        return

        lookForBuildFailPopup:
        IfWinActive, Microsoft Visual Studio, There were build errors
        {
        ControlFocus, No
        Send {Space}
        Sleep, 2000
        }
        return

      • Pratap Lakshman [MSFT]Pratap Lakshman [MSFT] commented  ·   ·  Flag as inappropriate

        I have added a comment/question to the new proposal linked below. Please let me know if I understood it correctly.

        Thank you for your feedback.

      • Matthew PiattMatthew Piatt commented  ·   ·  Flag as inappropriate

        +1 for turning off this dialog. This makes true Test Driven Development (TDD) a huge pain when using Visual Studio.

      • AlanAlan commented  ·   ·  Flag as inappropriate

        Ditto that. When build errors occur, I *NEVER* want to run. Dialog is a nuisance.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Yes, please reconsider this. The ask isn't to automatically run tests against the last build - those are useless if the code is broken. The ask is to get rid of the annoying dialog and run no tests at all.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        +1 to the "... missed thne point" comment. I never want to tests to run if my code didn't build as any results are misleading at best.

      • Ed KolisEd Kolis commented  ·   ·  Flag as inappropriate

        What about the ability to turn it permanently OFF, so we don't get nagged about running obsolete tests?

      • Anonymous commented  ·   ·  Flag as inappropriate

        I think you've missed the point. The issue with the message is that running tests from the previous build is never the correct thing to do. If I've chosen to run tests then I clearly want to test the current state of the code, not some historical version. If I run tests on the previous build then any result I get from the test is useless since I don't know what was actually in that build unless it's in source control, in which case I can just get the previous version. All the message does is get in the way of the standard process, which is to immediately fix whatever caused the build to fail.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please remove the popup from the default code path. No-one ever wants to run the tests from a previous build.

      • Bad KittyBad Kitty commented  ·   ·  Flag as inappropriate

        More generally, with just about any popup, there should be an option to prevent it from showing and automatically take whatever choice.

      Feedback and Knowledge Base