Open
Description
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:
- Open Test Explorer
- Run All Tests
- Assuming all tests pass, then attempt to run Failed Tests.
- 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.
- Close the Test Explorer
- 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
Labels
Identifies work items for known bugsThere is some way of working around this limitation / bug that is confirmed to workUse this label in conjunction with a difficulty level label, e.g. difficulty-02-duckyThis issue explicitly relates to the visible interface of Rubberduck.Issue is easier to resolve with knowledge of WPF/XAML
Type
Projects
Status
Backlog | Unit Testing