Bug Report T679365
Visible to All Users

Unit Testing - The Details section in the Test Runner window is cleared after editing a test

created 6 years ago

Hi,

I often create one unit test function with multiple TestCases, then run all test cases to see the results. When several test cases fail, I check the Details tab for the first failing test in the Test Runner to understand the reason for the failure, edit the TestCase or function to fix the test. When I then go to look at the Details for the next failing test case, it's cleared.

I understand that the details may not longer be current after editing the test, but this is really quite annoying, as I then need wait for the test to run again to see why the other test cases failed.

Can the test result details be preserved? Maybe the details could just be marked as non-current in some way (greyed out or coloured differently), instead of cleared, when the tests have been edited?

Additionally, it would be nice, if the "ready to run" icon, could have a different colour to highlight tests which have previously failed.

Comments (1)
PW PW
Przemyslaw Wlodarczak (DevExpress) 6 years ago

    Hi Dave,

    Thank you for the report. We will try to improve Test Runner behavior in the scenario you described. We will notify you here about our progress. Please bear with us.

    Answers approved by DevExpress Support

    created 6 years ago (modified 6 years ago)

    We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

    Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

      Show previous comments (5)
      PW PW
      Przemyslaw Wlodarczak (DevExpress) 6 years ago

        Dave,

        I am happy to hear that the issue is gone now.
        Regarding the change in behavior - the old behavior was incorrect and so we fixed it. We think the tests should keep their state when you are editing the code. We agree with you - it is more convenient when you don't need to re-run the tests in order to check why they failed. The state change you observe when editing the parameters in the TestCase attribute is not a reset of the test state. In reality you remove one test (identified by old parameter values) and create a new one with new parameter values. The test with the "failed" state gets removed from the suite and a new test which was not yet run gets added. It looks like we reset the test state, but it is a quite different scenario. I hope this clarifies things a bit.

          That makes sense. Thanks

          PW PW
          Przemyslaw Wlodarczak (DevExpress) 6 years ago

            You are welcome.

            Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

            Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.