Closed Deedolith closed 2 years ago
FWIW - I could not reproduce this issue following the steps described above (Excel host). It behaved as intended, so ATM this appears to be an intermittent failure.
From the graphic, it looks like the issue was observed on the first TestMethod
added to the first TestModule
...so I tried that scenario, again with success. And, finally...I went thru the steps when the project was in a 'non-compilable' state. Still worked as expected.
Guess it comes from my Office vesrion, I did not experience the same behavior with Office 2016.
Rubberduck version information The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
Version 2.5.2.6027 OS: Microsoft Windows NT 10.0.19043.0, x64 Host Product: Microsoft Office 2013 x64 Host Version: 15.0.5349.1000 Host Executable: MSACCESS.EXE
Description Within the Test Explorer window, after adding a Test Module, nothing new show up in the Test Explorer window. The "ducks" loading trails keep showing forever.
To Reproduce Steps to reproduce the behavior:
Expected behavior A new line holding tests informations should show up in the Test Window
Screenshots
Logfile RubberduckLog.txt
Additional context Behavior observer within both MS Access and MS Excel (2013).