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

Doctest Regression in 4.5. All tests that previously executed and passed, are now "Skipped" #392

Closed
5 tasks done
richyo-work opened this issue Jul 26, 2023 · 2 comments
Closed
5 tasks done

Comments

@richyo-work
Copy link

richyo-work commented Jul 26, 2023

Checklist

  • The issue is about this extension and NOT about a fork.
  • Check the known issues list.
  • The latest version of the extension was used.
  • It is not related to remote-vscode or I checked the following issue
  • Imagine yourself into my position and think how hard to debug the issue without insufficient information.
    I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
    Thanks.

Describe the bug

Since version 4.5, all my doctests continue to be discovered, however attempting to run them now longer shows pass or fail. They all show skipped

To Reproduce

#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN 
#include "doctest.h"

TEST_CASE("first test") {

}


TEST_CASE("second test") {

}

image

Desktop

  • Extension Version:
  • VS Code Version: 1.80
  • Catch2 / Google Test / DOCTest Version:
  • OS Type and Version: Windows 10, Windows 11
  • Using remote-ssh/docker/wsl?: no

Regression bug?
The previous release 4.4 works. The doctest bug fixes in 4.5 are causing a regression for me.

I've validated this on Windows 10, and Windows 11

Log (optional but recommended)

Note I will follow up with more information

@lostfalter
Copy link

I have the same issue on the Mac.

@matepek
Copy link
Owner

matepek commented Jul 26, 2023

Fixed in v4.5.1.

This issue was mentioned in CHANGELOG.md under a released entry so it is assumed to be fixed.
User verifications are always welcome.

@matepek matepek closed this as completed Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants