Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rubberduck>UnitTest>Run All Tests doesn't update the grouping headers #3738

Closed
IvenBach opened this issue Jan 30, 2018 · 1 comment · Fixed by #4769
Closed

Rubberduck>UnitTest>Run All Tests doesn't update the grouping headers #3738

IvenBach opened this issue Jan 30, 2018 · 1 comment · Fixed by #4769
Assignees
Labels
bug Identifies work items for known bugs feature-unit-testing regression This used to work, but something broke it. Fixes should involve a regression test, if possible
Milestone

Comments

@IvenBach
Copy link
Member

Below is what is shown when run through Rubberduck>Unit Test>Run All Tests
rubberduck unittests runalltests

Below the grouping headers update appropriately if from the TestExplorer window Run button
runbutton on testexplorer

@Vogel612 Vogel612 added bug Identifies work items for known bugs feature-unit-testing labels Jan 30, 2018
@IvenBach
Copy link
Member Author

IvenBach commented Feb 10, 2018

The times aren't updating either. It's probably the same issue but wanted to document nonetheless.
capture

@Vogel612 Vogel612 added the regression This used to work, but something broke it. Fixes should involve a regression test, if possible label Feb 20, 2018
@comintern comintern self-assigned this Feb 4, 2019
Semi-automatic bug tracker automation moved this from ToDo to Done Feb 19, 2019
@Vogel612 Vogel612 added this to the 2.4.1 milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies work items for known bugs feature-unit-testing regression This used to work, but something broke it. Fixes should involve a regression test, if possible
Projects
Development

Successfully merging a pull request may close this issue.

3 participants