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

[Catch2] Custom main file not being picked up #422

Closed
ricardomatias opened this issue Feb 8, 2024 · 3 comments
Closed

[Catch2] Custom main file not being picked up #422

ricardomatias opened this issue Feb 8, 2024 · 3 comments

Comments

@ricardomatias
Copy link

Checklist

  • [x ] The issue is about this extension and NOT about a fork.
  • [ x] Checked the ALL the SUPPORT document.
  • [x ] The latest version of the extension was used.
  • [x ] It is not related to remote-vscode or I checked the following issue
  • [x ] 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

I've got a working cmake configuration that allows me to use ApprovalTests.cpp with catch2. It does so by creating an executable for each file depending on a custom main.cpp file and then the test file. This doesn't seem to work with Testmate, the test case where ApprovalTests is used exits with a FatalErrorCondition which I've traced to the ApprovalTests library not being initialized (which happens on the custom main_config.cpp file). I've added the "_config" to the pattern finding configuration but to no avail. Am I doing something wrong?

Desktop

  • Extension Version: 4.8.3
  • VS Code Version: 1.86.0
  • Catch2 / Google Test / DOCTest Version: 3.3.2
  • OS Type and Version: Mac OS 13.6.3
  • Using remote-ssh/docker/wsl?: No
@matepek
Copy link
Owner

matepek commented Feb 8, 2024

Is this ApprovalTest a dynamically linked library?

@matepek
Copy link
Owner

matepek commented Feb 8, 2024

Can you run your exec from command line?
try to check the logs.

@ricardomatias
Copy link
Author

@matepek I ran from the command line and the error was the same, so this is not a problem with this extension. Thanks for the help.

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

2 participants