Skip to content

Test Explorer becomes unresponsive if attempt is made to run Failed Tests when there are no failed tests #5665

Open
@BZngr

Description

@BZngr

Version 2.5.1.33112
OS: Microsoft Windows NT 10.0.18363.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.13628.20274
Host Executable: EXCEL.EXE

Description
If a request is made within the Test Explorer to run Failed Tests, but there are no previously failed tests - the 'Run' portion of the Test Explorer becomes unresponsive.

To Reproduce
Steps to reproduce the behavior:

  1. Open Test Explorer
  2. Run All Tests
  3. Assuming all tests pass, then attempt to run Failed Tests.
  4. See error. Closing an re-opening the Test Explorer does not clear the problem

Expected behavior
Test Explorer 'Run' menu should remain responsive. And perhaps a message indicating "no failed tests found".

There is a workaround.

  1. Close the Test Explorer
  2. From the VBE , select "Rubberduck -> Unit Tests -> Run All Tests".
    The tests will run and the Test Explorer (when re-opened) is again responsive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIdentifies work items for known bugsfeature-unit-testinghas-workaroundThere is some way of working around this limitation / bug that is confirmed to workup-for-grabsUse this label in conjunction with a difficulty level label, e.g. difficulty-02-duckyuser-interfaceThis issue explicitly relates to the visible interface of Rubberduck.wpfIssue is easier to resolve with knowledge of WPF/XAML

    Type

    No type

    Projects

    Status

    Backlog | Unit Testing

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions